Current Build
FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: Informative

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

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

NameDefinitionSourceId
Namespace: http://hl7.org/fhir/ValueSet
FHIR-version NAll published FHIR Versions.Internal1309
abstract-types NA list of the base types defined by this version of the FHIR specification - types that are defined, but for which only specializations actually are created.Internal23
account-statusIndicates whether the account is available to be used.Internal726
account-typeThis examples value set defines the set of codes that can be used to represent the type of an account.V3728
action-cardinality-behaviorDefines behavior for an action or a group for how many times that item may be repeated.Internal807
action-condition-kindDefines the kinds of conditions that can appear on actions.Internal815
action-grouping-behaviorDefines organization behavior of a group.Internal799
action-participant-roleEither a practitioner role or a relationship type.Other796
action-participant-typeThe type of participant for the action.Internal811
action-precheck-behaviorDefines selection frequency behavior for an action or group.Internal805
action-relationship-typeDefines the types of relationships between actions.Internal813
action-required-behaviorDefines expectations around whether an action or action group is required.Internal803
action-selection-behaviorDefines selection behavior of a group.Internal801
action-typeThe type of action to be performed.Other809
activity-definition-categoryHigh-level categorization of the type of activity.Other792
additional-instruction-codesThis value set includes all SNOMED CT Additional Dosage Instructions.SNOMED CT95
additionalmaterialsThis value set includes sample additional material type codes.Internal529
address-type NThe type of an address (physical / postal).Internal69
address-use NThe use of an address.Internal67
adjudicationThis value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc.Other596
adjudication-errorThis value set includes a smattering of adjudication codes.Other39
adjudication-reasonThis value set includes smattering of Adjudication Reason codes.Other598
administration-method-codesThis value set includes some method codes from SNOMED CT - provided as an exemplarSNOMED CT97
administrative-gender NThe gender of a person used for administrative purposes.Internal1
adverse-event-actualityOverall nature of the event, e.g. real or potential.Internal831
adverse-event-categoryOverall categorization of the event, e.g. product related or situational.Other833
adverse-event-causality-assessTODO.Other840
adverse-event-causality-methodTODO.Other842
adverse-event-outcomeTODO (and should this be required?).Other836
adverse-event-seriousnessOverall seriousness of this event for the patient.Other838
adverse-event-severityThe severity of the adverse event itself, in direct relation to the subject.Other844
adverse-event-typeThis value set includes all SNOMED CT Clinical Findings.SNOMED CT835
age-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR19
all-distance-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of lengthFHIRnull
all-languages NThis value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47)Other21
all-time-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codes for units of timeFHIRnull
all-types NA list of all the concrete types defined in this version of the FHIR specification - Abstract Types, Data Types and Resource Types.Internal25
allelenameEuropean Bioinformatics InstituteOther1045
allerg-intol-substance-exp-riskThe risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products).Other940
allergy-intolerance-categoryCategory of an identified substance.Internal133
allergy-intolerance-criticalityEstimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.Internal129
allergy-intolerance-typeIdentification of the underlying physiological mechanism for a Reaction Risk.Internal131
allergyintolerance-clinicalPreferred value set for AllergyIntolerance Clinical Status.Other1372
allergyintolerance-codeThis 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 CT137
allergyintolerance-verificationPreferred value set for AllergyIntolerance Verification Status.Other1370
animal-breedsThis example value set defines a set of codes that can be used to indicate breeds of species.SNOMED CT422
animal-genderstatusThis example value set defines a set of codes that can be used to indicate the current state of the animal's reproductive organs.Internal418
animal-speciesThis example value set defines a set of codes that can be used to indicate species of animal patients.SNOMED CT420
appointment-cancellation-reasonThis example value set defines a set of reasons for the cancellation of an appointment.Other0
appointmentstatusThe free/busy status of an appointment.Internal484
approach-site-codesThis value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar.SNOMED CT346
assert-direction-codesThe type of direction to use for assertion.Internal706
assert-operator-codesThe type of operator to use for assertion.Internal708
assert-response-code-typesThe type of response code to use for assertion.Internal710
asset-availabilityThis value set has asset availability codes.Internal1295
audit-entity-typeCode for the entity type involved in the audit event.Other, Internal458
audit-event-actionIndicator for type of action performed during the event that generated the event.Internal452
audit-event-outcomeIndicates whether the event succeeded or failed.Internal454
audit-event-sub-typeMore detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions.DICOM, Internal464
audit-event-typeEvent Types for Audit Events - defined by DICOM with some FHIR specific additions.DICOM, Other462
audit-source-typeThe type of process where the audit event originated from.Other466
basic-resource-typeThis 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.Other138
benefit-networkThis value set includes a smattering of Network type codes.Other608
benefit-termThis value set includes a smattering of Benefit Term codes.Other612
benefit-typeThis value set includes a smattering of Benefit type codes.Other606
benefit-unitThis value set includes a smattering of Unit type codes.Other610
binding-strength NIndication of the degree of conformance expectations associated with a binding.Internal43
body-siteThis value set includes all codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 442083009 (Anatomical or acquired body site (body structure)).SNOMED CT141
bodysite-lateralityLaterality: SNOMED-CT concepts for 'left', 'right', and 'bilateral'SNOMED CT287
bodystructure-codeThis value set includes all codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 442083009 (Anatomical or acquired body site (body structure)).SNOMED CT142
bodystructure-relative-locationSNOMED-CT concepts modifying the anatomic locationSNOMED CT140
bundle-type NIndicates the purpose of a bundle - how it is intended to be used.Internal620
c80-doc-typecodesThis 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.LOINC47
c80-facilitycodesThis 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 CT67
c80-practice-codesThis 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 CT72
capability-statement-kind NHow a capability statement is intended to be used.Internal198
care-plan-activity-kindResource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.Internal145
care-plan-activity-outcomeExample codes indicating the outcome of a care plan activity. Note that these are in no way complete and might not even be appropriate for some uses.SNOMED CT149
care-plan-activity-statusIndicates where the activity is at in its overall life cycle.Internal146
care-plan-categoryExample codes indicating the category a care plan falls within. Note that these are in no way complete and might not even be appropriate for some uses.SNOMED CT148
care-plan-intentCodes indicating the degree of authority/intentionality associated with a care plan.Internal150
care-team-categoryIndicates the type of care team.LOINC155
care-team-statusIndicates the status of the care team.Internal153
catalogTypeThe type of catalog.Other968
cdshooks-indicatorThis value set captures the set of indicator codes defined by the CDS Hooks specification.Other1065
certainty-subcomponent-ratingThe quality rating of the subcomponent of a quality of evidence rating.Other1361
certainty-subcomponent-typeThe subcomponent classification of quality of evidence rating systems.Other1359
chargeitem-billingcodesExample set of codes that can be used for billing purposes.Other848
chargeitem-statusCodes identifying the lifecycle stage of a ChargeItem.Internal846
choice-list-orientationDirection in which lists of possible answers should be displayed.Other933
chromosome-humanChromosome number for human.Other224
claim-careteamroleThis value set includes sample Claim Care Team Role codes.Other586
claim-exceptionThis value set includes sample Exception codes.Other580
claim-informationcategoryThis value set includes sample Information Category codes.Other582
claim-modifiersThis value set includes sample Modifier type codes.Other536
claim-subtypeThis value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bed stay and transportation.Other566
claim-typeThis value set includes Claim Type codes.Other558
claim-useThe purpose of the Claim: predetermination, preauthorization, claim.Internal544
clinical-findingsThis value set includes all the "Clinical finding" [SNOMED CT](http://snomed.info/sct) codes - concepts where concept is-a 404684003 (Clinical finding (finding)).SNOMED CT232
clinicalimpression-prognosisExample value set clinical impression prognosisSNOMED CT160
clinicalimpression-statusCodes identifying the lifecycle stage of a clinical impressionInternal1046
clinvarNCBI central repository for curating pathogenicity of potentially clinically relevant variantsOther1041
code-search-supportThe degree to which the server supports the code search parameter on ValueSet, if it is supported.Internal860
codesystem-altcode-kindIndicates the type of use for which the code is defined.Other952
codesystem-content-mode NThe extent of the content of the code system (the concepts and codes it defines) are represented in a code system resource.Internal782
codesystem-hierarchy-meaning NThe meaning of the hierarchy of concepts in a code system.Internal784
common-tagsCommon Tag Codes defined by FHIR projectOther79
communication-categoryCodes for general categories of communications such as alerts, instruction, etc.Other172
communication-not-done-reasonCodes for the reason why a communication was not done.Other174
communication-topicCodes describing the purpose or content of the communication.Other983
compartment-typeWhich type a compartment definition describes.Internal786
composite-measure-scoringThe composite scoring method of the measure.Other773
composition-altcode-kindIndicates the type of use for which the code is defined.Other0
composition-attestation-modeThe way in which a person authenticated a composition.Internal238
composition-statusThe workflow/clinical status of the composition.Internal241
concept-map-equivalenceThe degree of equivalence between concepts.Internal17
concept-property-type NThe type of a property value.Internal780
concept-subsumption-outcomeThe subsumption relationship between code/Coding "A" and code/Coding "B". There are 4 possible codes to be returned: equivalent, subsumes, subsumed-by, and not-subsumed. If the server is unable to determine the relationship between the codes/Codings, then it returns an error (i.e. an OperationOutcome).Internal1238
conceptmap-unmapped-modeDefines which action to take if there is no match in the group.Internal480
condition-categoryPreferred value set for Condition Categories.Other162
condition-causeExample value set for Cause of Condition codesSNOMED CT965
condition-clinicalPreferred value set for Condition Clinical Status.Other164
condition-codeExample value set for Condition/Problem/Diagnosis codesSNOMED CT161
condition-outcomeExample value set for Condition OutcomesSNOMED CT967
condition-predecessorExample value set for Condition Predecessor codesSNOMED CT966
condition-severityPreferred value set for Condition/Diagnosis severity gradingSNOMED CT168
condition-stageExample value set for stages of cancer and other conditionsSNOMED CT170
condition-stage-typeExample value set for the type of stages of cancer and other conditionsSNOMED CT171
condition-stateEnumeration indicating whether the condition is currently active, inactive, or has been resolved.Other963
condition-ver-statusThe verification status to support or decline the clinical status of the condition or diagnosis.Other166
conditional-delete-status NA code that indicates how the server supports conditional delete.Internal194
conditional-read-status NA code that indicates how the server supports conditional read.Internal200
conformance-expectationIndicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification.Other919
consent-actionThis value set includes sample Consent Action codes.Other753
consent-categoryThis value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes; HL7 VALUE SET: ActConsentType(2.16.840.1.113883.1.11.19897); examples of US realm consent directive legal descriptions and references to online and/or downloadable forms such as the SSA-827 Authorization to Disclose Information to the Social Security Administration; and other anticipated consent directives related to participation in a clinical trial, medical procedures, reproductive procedures; health care directive (Living Will); advance directive, do not resuscitate (DNR); Physician Orders for Life-Sustaining Treatment (POLST)Other, LOINC751
consent-content-classThis value set includes the FHIR resource types, along with some other important content class codesOther, Internal747
consent-content-codeThis example value set contains all LOINC codeLOINC748
consent-data-meaningHow a resource reference is interpreted when testing consent restrictions.Internal759
consent-performerThis value set includes sample Performer Role codes.Internal1016
consent-policyThis value set includes sample Regulatory consent policy types from the US and other regions.Other1014
consent-provision-typeHow a rule statement is applied, such as adding additional consent or removing consent.Internal757
consent-scopeThis value set includes the four Consent scope codes.Other761
consistency-typeFluidConsistencyType : Codes used to represent the consistency of fluids and liquids provided to the patient. This value set includes concepts from [SNOMED CT](http://snomed.info/sct)(US Extension) where concept is a 435681000124103 (Dietary liquid consistency diet (regime/therapy)). It is provided as a suggestive example.SNOMED CT389
constraint-severity NSHALL applications comply with this constraint?Internal81
contact-point-system NTelecommunications form for contact point.Internal71
contact-point-use NUse of contact point.Internal73
contactentity-typeThis example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party.Other416
container-capColor of the container cap.Other850
container-materialThis value set includes SNOMED CT codes for materials that specimen containers are made ofSNOMED CT0
contract-actionThis value set includes sample Contract Action codes.Other739
contract-actionstatusThis value set contract specific codes for action status.Internal1303
contract-actorroleThis value set includes sample Contract Actor Role codes.Other741
contract-assetcontextThis value set contract specific codes for asset context.Internal1297
contract-assetscopeThis value set contract specific codes for asset scope.Internal1293
contract-assetsubtypeThis value set contract specific codes for asset subtype.Internal1301
contract-assettypeThis value set contract specific codes for asset type.Internal1299
contract-content-derivativeThis is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses.Other745
contract-data-meaningHow a resource reference is interpreted when evaluating contract offers.Other749
contract-decision-modeThis value set contract specific codes for decision modes.Internal1291
contract-definition-subtypeThis value set contract specific codes for status.Internal1212
contract-definition-typeThis value set contract specific codes for status.Internal1210
contract-expiration-typeThis value set contract specific codes for status.Internal1214
contract-legalstateThis value set contract specific codes for status.Internal1206
contract-party-roleThis value set contract specific codes for offer party participation.Internal1224
contract-publicationstatusThis value set contract specific codes for status.Internal1208
contract-scopeThis value set contract specific codes for scope.Internal1216
contract-security-categoryThis value set contract specific codes for security category.Internal1220
contract-security-classificationThis value set contract specific codes for security classification.Internal1218
contract-security-controlThis value set contract specific codes for security control.Internal1222
contract-signer-typeThis value set includes sample Contract Signer Type codes.Other737
contract-statusThis value set contract specific codes for status.Internal743
contract-subtypeThis value set includes sample Contract Subtype codes.Other731
contract-term-subtypeThis value set includes sample Contract Term SubType codes.Other735
contract-term-typeThis value set includes sample Contract Term Type codes.Other733
contract-typeThis value set includes sample Contract Type codes.Other729
contributor-typeThe type of contributor.Internal93
copy-number-eventCopy Number Event.Other226
cosmicCOSMIC : Catalogue Of Somatic Mutations In CancerOther912
coverage-classThis value set includes Coverage Class codes.Other1009
coverage-copay-typeThis value set includes sample Coverage Copayment Type codes.Other527
coverage-financial-exceptionThis value set includes Example Coverage Financial Exception Codes.Other1328
coverage-selfpayThis value set includes Coverage SelfPay codes.Other525
coverage-typeThis value set includes Coverage Type codes.Other520
cpt-allA value set that includes all CPT codesOthernull
currencies NCurrency codes from ISO 4217 (see https://www.iso.org/iso-4217-currency-codes.html)Other1025
data-absent-reason NUsed to specify why the normally expected content of the data element is missing.Other5
data-types NA version specific list of the data types defined by the FHIR specification for use as an element type (any of the FHIR defined data types).Internal22
dataelement-sdcobjectclassThe 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, Other910
dataelement-sdcobjectclasspropertyThe 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, Other911
days-of-week NThe days of the week.Internal512
dbsnpDBSNP : Single Nucleotide Polymorphism databaseOther284
defined-types NA list of all the concrete types defined in this version of the FHIR specification - Data Types and Resource Types.Internal24
definition-resource-typesA list of all the definition resource types defined in this version of the FHIR specification.Internal1056
definition-statusCodes identifying the lifecycle stage of a definition.Other107
definition-topicHigh-level categorization of the definition, used for searching, sorting, and filtering.Other794
definition-use NStructure Definition Use Codes / KeywordsOther1190
designation-use NDetails of how a designation would be usedSNOMED CT264
detectedissue-categoryKinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc.V3204
detectedissue-mitigation-actionKinds of mitigating actions and observations that can be associated with a detected issue or contraindication, such as 'added concurrent therapy', 'prior therapy documented', etc.V3205
detectedissue-severityIndicates the potential degree of impact of the identified issue on the patient.Internal206
device-actionExample codes indicating the change that happened to the device during the procedure. Note that these are in no way complete and might not even be appropriate for some uses.SNOMED CT425
device-component-propertyCodes for identifying device properties. This is based upon IEEE/HCD specified codes.Other634
device-definition-statusCodes representing the current status of the device - on, off, suspended, etc.Internal1307
device-kindCodes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.SNOMED CT208
device-nametypeThe type of name the device is referred by.Internal1083
device-safetyCodes used to identify medical devices safety characteristics. These codes are taken from the [NCI Thesaurus](https://ncit.nci.nih.gov/ncitbrowser/pages/home.jsf) and are provided here as a suggestive example.Other213
device-statement-statusA coded concept indicating the current status of the Device Usage.Internal214
device-statusThe availability status of the device.Internal209
device-status-reasonThe availability status reason of the device.Other1081
device-typeCodes used to identify medical devices. Includes concepts from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.SNOMED CT0
devicemetric-typeCodes used to identify health care device metric types and units and component types as part of the ISO/IEEE 11073-10101 Medical Device Communication Nomenclature.Other645
diagnosis-roleThis value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record.Other49
diagnostic-based-on-snomedDiagnostic Attachment Type codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182836005 (Review of medication (procedure)) or is-a 404684003 (Clinical finding (finding))SNOMED CT960
diagnostic-report-statusThe status of the diagnostic report.Internal235
diagnostic-service-sectionsThis value set includes all the codes in HL7 V2 table 0074.V2234
dicm-405-mediatypeMedia Type CodeDICOM​908
diet-typeCodes that can be used to indicate the type of food being ordered for a patient. This value set is provided as a suggestive example. It includes codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182922004 (Dietary regime (regime/therapy)) SNOMED CT385
discriminator-type NHow an element value is interpreted when discrimination is evaluated.Internal91
distance-unitsUnified Code for Units of Measure (UCUM). This value set includes common UCUM codes for units of distanceFHIR62
doc-section-codesDocument section codes (LOINC codes used in CCDA sections).LOINC237
doc-typecodesFHIR Document Codes - all LOINC codes where scale type = 'DOC'.LOINC240
document-classcodesThis is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests.LOINC46
document-mode NWhether the application produces or consumes documents.Internal186
document-reference-statusThe status of the document reference.Internal7
document-relationship-typeThe type of relationship between documents.Internal244
dose-rate-typeThe kind of dose or rate specified.Other981
duration-units NUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR61
effect-estimate-typeWhether the effect estimate is an absolute effect estimate (absolute difference) or a relative effect estimate (relative difference), and the specific type of effect estimate (eg relative risk or median difference).Other1355
eligibilityrequest-purposeA code specifying the types of information being requested.Internal1182
eligibilityresponse-purposeA code specifying the types of information being requested.Internal1184
encounter-admit-sourceThis value set defines a set of codes that can be used to indicate from where the patient came in.Other257
encounter-dietThis value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.Other255
encounter-discharge-dispositionThis value set defines a set of codes that can be used to where the patient left the hospital.Other259
encounter-location-statusThe status of the location.Internal262
encounter-participant-typeThis value set defines a set of codes that can be used to indicate how an individual participates in an encounter.V3, Other250
encounter-reasonThis examples value set defines the set of codes that can be used to indicate reasons for an encounter.SNOMED CT261
encounter-special-arrangementsThis value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit.Other253
encounter-special-courtesyThis value set defines a set of codes that can be used to indicate special courtesies provided to the patient.V3252
encounter-statusCurrent state of the encounter.Internal246
encounter-typeThis 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.Other248
endpoint-connection-typeThis is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.Other498
endpoint-payload-typeThis is an example value set defined by the FHIR project, that could be used to represent possible payload document types.Other496
endpoint-statusThe status of the endpoint.Internal494
ensemblENSEMBL reference sequence identifiersOther1040
enteral-routeEnteralRouteOfAdministration: 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.V3394
entformula-additiveEnteralFormulaAdditiveType: 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.Other392
entformula-typeEnteralFormulaType : Codes for type of enteral formula to be administered to patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example.SNOMED CT391
episode-of-care-statusThe status of the episode of care.Internal664
episodeofcare-typeThis example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.Other666
event-capability-mode NThe mode of a message capability statement.Internal182
event-or-request-resource-typesThis value set lists all the event or request resource types defined in this version of the specification.Other1064
event-resource-typesA list of all the event resource types defined in this version of the FHIR specification.Internal1060
event-statusCodes identifying the lifecycle stage of an event.Internal109
event-timing NReal world event relating to the schedule.Internal, V375
evidence-qualityA rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems.Other1020
evidence-variant-stateUsed for results by exposure in variant states such as low-risk, medium-risk and high-risk states.Other1353
ex-benefitcategoryThis value set includes examples of Benefit Category codes.Other1174
ex-diagnosis-on-admissionThis value set includes example Diagnosis on Admission codes.Other1169
ex-diagnosisrelatedgroupThis value set includes example Diagnosis Related Group codes.Other588
ex-diagnosistypeThis value set includes example Diagnosis Type codes.Other590
ex-onsettypeThis value set includes sample Service Modifier codes.Internal578
ex-payee-resource-typeThe type of Claim payee Resource.Other584
ex-paymenttypeThis value set includes example Payment Type codes.Other616
ex-procedure-typeThis value set includes example Procedure Type codes.Other0
ex-program-codeThis value set includes sample Program Reason Span codes.Other576
ex-revenue-centerThis value set includes sample Revenue Center codes.Other594
example-expansionThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINCnull
example-extensionalThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINCnull
example-filterACME Codes for Cholesterol: Plasma only - demonstrating the use of a filter defined in a CodeSystemInternalnull
example-hierarchicalDemonstration of extensions that build a hierarchical containsOthernull
example-intensionalThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINCnull
examplescenario-actor-typeThe type of actor - system or human.Internal858
expansion-parameter-sourceDeclares what the source of a parameter is.Other1278
expansion-processing-ruleDefines how concepts are processed into the expansion when it's for UI presentation.Other1280
explanationofbenefit-statusA code specifying the state of the resource instance.Internal618
exposure-stateWhether the results by exposure is describing the results for the primary exposure of interest (exposure) or the alternative state (exposureAlternative).Internal1351
expression-languageThe media type of the expression language.Internal105
extension-context-type NHow an extension context is interpreted.Internal1012
feeding-deviceMaterials used or needed to feed the patient.Internal, SNOMED CT961
filter-operator NThe kind of operation to perform as a part of a property based filter.Internal478
financial-taskcodeThis value set includes Financial Task codes.Other0
financial-taskinputtypeThis value set includes Financial Task Input Type codes.Other0
flag-categoryExample list of general categories for flagged issues. (Not complete or necessarily appropriate.)Other122
flag-codeExample list of detail codes for flagged issues. (Not complete or necessarily appropriate.)SNOMED CT124
flag-priorityThis value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority.Internal950
flag-statusIndicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or entered in error.Internal120
fm-conditionsThis value set includes sample Conditions codes.Internal556
fm-itemtypeThis value set includes sample Item Type codes.Internal548
fm-statusThis value set includes Status codes.Internal592
focal-subjectExample value set composed from SNOMED CT and HL7 V3 codes for observation targets such as donor, fetus or spouse. As use cases are discovered, more values may be added.SNOMED CT, V3954
food-typeThis value set represents codes for types of foods and is provided as a suggestive example. It include codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 255620007 (Foods (substance)).SNOMED CT384
formatcodesThe value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at https://confluence.hl7.org/display/SD/Format+Codes+for+IHE+XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incompleteOther1
formsThis value set includes a sample set of Forms codes.Other37
fundsreserveThis value set includes sample funds reservation type codes.Other33
gender-identityThis example value set defines a set of codes that can be used to indicate a patient's gender identity.Internal972
genenamesHGNC: Human Gene Nomenclature CommitteeOther281
goal-acceptance-statusCodes indicating whether the goal has been accepted by a stakeholder.Other917
goal-achievementDescribes the progression, or lack thereof, towards the goal against the target .Other1374
goal-categoryExample codes for grouping goals for filtering or presentation.Other275
goal-priorityIndicates the level of importance associated with reaching or sustaining a goal.Other273
goal-relationship-typeTypes of relationships between two goals.Other915
goal-start-eventIdentifies types of events that might trigger the start of a goal.SNOMED CT279
goal-statusIndicates whether the goal has been met and is still being targeted.Internal271
goal-status-reasonExample codes indicating the reason for a current status. Note that these are in no way complete and might not even be appropriate for some uses.Internal277
graph-compartment-ruleHow a compartment must be linked.Internal280
graph-compartment-useDefines how a compartment rule is used.Internal282
group-measurePossible group measure aggregates (E.g. Mean, Median).Internal1345
group-typeTypes of resources that are part of group.Internal284
guidance-response-statusThe status of a guidance response.Internal817
guide-page-generationA code that indicates how the page is generated.Internal998
guide-parameter-codeCode of parameter that is input to the guide.Internal996
handling-conditionSet of handling instructions prior testing of the specimen.Other854
history-absent-reasonCodes describing the reason why a family member's history is not available.Other269
history-statusA code that identifies the status of the family history record.Internal267
hl7-work-groupAn HL7 administrative unit that owns artifacts in the FHIR specification.Other944
http-operationsThe allowable request method or HTTP operation codes.Internal716
http-verb NHTTP verbs (in the HTTP command line). See [HTTP rfc](https://tools.ietf.org/html/rfc7231) for details.Internal624
icd-10This value set includes sample ICD-10 codes.Internal531
icd-10-proceduresThis value set includes sample ICD-10 Procedure codes.Internal574
identifier-type NA coded type for an identifier that can be used to determine which identifier to use for a specific purpose.V245
identifier-use NIdentifies the purpose for this identifier, if known .Internal57
identity-assuranceLevelThe level of confidence that this link represents the same actual person, based on NIST Authentication Levels.Internal656
imagingstudy-statusThe status of the ImagingStudy.Internal990
immunization-evaluation-dose-statusThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example.Other301
immunization-evaluation-dose-status-reasonThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example.Other303
immunization-evaluation-statusThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the current status of the evaluation for vaccine administration event.Other299
immunization-evaluation-target-diseaseThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the disease that the evaluation is against. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy.SNOMED CT300
immunization-functionThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the function a practitioner or organization may play in the immunization event. This value set is provided as a suggestive example.V2995
immunization-funding-sourceThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example.Other293
immunization-originThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the data when the report of the immunization event is not based on information from the person, entity or organization who administered the vaccine. This value set is provided as a suggestive example.Other296
immunization-program-eligibilityThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's eligibility for a vaccination program. This value set is provided as a suggestive example.Other291
immunization-reasonThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was administered. This value set is provided as a suggestive example.SNOMED CT290
immunization-recommendation-date-criterionThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support the definition of dates relevant to recommendations for future doses of vaccines. This value set is provided as a suggestive example.LOINC308
immunization-recommendation-reasonThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reasons why a given recommendation status is assigned. This value set is provided as a suggestive example and includes SNOMED CT concepts.SNOMED CT307
immunization-recommendation-statusThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example.Other305
immunization-recommendation-target-diseaseThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the disease targeted by a vaccination recommendation. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy.SNOMED CT309
immunization-routeThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the administrative routes used during vaccination. This value set is provided as a suggestive example.V3289
immunization-siteThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the body site where the vaccination occurred. This value set is provided as a suggestive example.V3288
immunization-statusThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the current status of the administered dose of vaccine.Internal295
immunization-status-reasonThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose of vaccine was not administered. This value set is provided as a suggestive example.V3, SNOMED CT992
immunization-subpotent-reasonThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example.Other993
immunization-target-diseaseThe value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the disease that the dose is being administered against. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy.SNOMED CT1047
implantStatusA set codes that define the functional status of an implanted device.Other1282
inactiveHL7 v3 ActMood Predicate codes, including inactive codesV3null
instance-availabilityAvailability of the resource.DICOM​811
insuranceplan-applicabilityWhether the cost applies to in-network or out-of-network providers.Other0
insuranceplan-typeThis example value set defines a set of codes that can be used to indicate a type of insurance plan.Other870
interventionThis value set includes sample Intervention codes.Internal532
investigation-setsExample value set for investigation typeSNOMED CT157
invoice-priceComponentTypeCodes indicating the kind of the price component.Internal868
invoice-statusCodes identifying the lifecycle stage of an Invoice.Internal866
iso3166-1-2This value set defines the ISO 3166 Part 1 2-letter codesOthernull
iso3166-1-3This value set defines the ISO 3166 Part 1 3-letter codesOthernull
iso3166-1-NThis value set defines the ISO 3166 Part 1 Numeric codesOthernull
issue-severity NHow the issue affects the success of the action.Internal408
issue-type NA code that describes the type of issue.Internal410
item-typeDistinguishes groups from questions and display text and indicates data type for questions.Internal444
jurisdiction NThis value set defines a base set of codes for country, country subdivision and region for indicating where a resource is intended to be used. Note: The codes for countries and country subdivisions are taken from [ISO 3166](https://www.iso.org/iso-3166-country-codes.html) while the codes for "supra-national" regions are from [UN Standard country or area codes for statistical use (M49)](http://unstats.un.org/unsd/methods/m49/m49.htm).Other48
knowledge-resource-typesA list of all the knowledge resource types defined in this version of the FHIR specification.Internal1062
language-preference-typeThis value set defines the set of codes for describing the type or mode of the patient's preferred language.Internal1022
languagesThis value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)Other20
ldlcholesterol-codesLDL Cholesterol codes - measured or calculatedLOINC959
library-typeThe type of knowledge asset this library contains.Other763
link-type NThe type of link between this patient resource and another patient resource.Internal423
linkage-typeUsed to distinguish different roles a resource can play within a set of linked resources.Internal314
list-empty-reasonGeneral 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).Other322
list-example-codesExample use codes for the List resource - typical kinds of use.Other316
list-item-flagExample 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.Other320
list-modeThe processing mode that applies to this list.Internal318
list-orderBase values for the order of the items in a list resource.Other324
list-statusThe current state of the list.Internal326
location-modeIndicates whether a resource instance represents a specific location or a class of locations.Internal330
location-physical-typeThis example value set defines a set of codes that can be used to indicate the physical form of the Location.Other328
location-statusIndicates whether the location is still in use.Internal332
manifestation-or-symptomExample value set for Manifestation and Symptom codes.SNOMED CT169
map-context-typeHow to interpret the context.Internal679
map-group-type-modeIf this is the default rule set to apply for the source type, or this combination of types.Internal687
map-input-modeMode for this instance of data.Internal677
map-model-modeHow the referenced structure is used in this mapping.Internal675
map-source-list-modeIf field is a list, how to manage the source.Internal683
map-target-list-modeIf field is a list, how to manage the production.Internal685
map-transformHow data is copied/created.Internal681
marital-status NThis value set defines the set of codes that can be used to indicate the marital status of a person.V329
match-gradeA Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not.Other970
measure-data-usageThe intended usage for supplemental data elements in the measure.Other771
measure-improvement-notationObservation values that indicate what change in a measurement value or score is indicative of an improvement in the measured item or scored issue.Other1236
measure-populationThe type of population.Other765
measure-report-statusThe status of the measure report.Internal776
measure-report-typeThe type of the measure report.Internal778
measure-scoringThe scoring type of the measure.Other767
measure-typeThe type of measure (includes codes from 2.16.840.1.113883.1.11.20368).Other769
med-admin-perform-functionMedicationAdministration Performer Function CodesOther349
media-modalityDetailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it.Other1001
media-typeCodes for high level media categories.Other1000
media-viewCodes defined in SNOMED CT that can be used to record Media Recording views.SNOMED CT337
medication-admin-categoryMedicationAdministration Category CodesOther347
medication-admin-statusMedicationAdministration Status CodesOther340
medication-as-needed-reasonThis value set includes all clinical findings from SNOMED CT - provided as an exemplar value set.SNOMED CT96
medication-codesThis value set includes all drug or medicament substance codes and all pharmaceutical/biologic products from SNOMED CT - provided as an exemplar value set.SNOMED CT375
medication-form-codesThis value set includes all dose form codes from SNOMED CT - provided as an exemplar.SNOMED CT374
medication-statement-categoryMedication Status CodesOther370
medication-statement-statusMedication Status CodesInternal367
medication-statusMedication Status CodesInternal376
medicationdispense-categoryMedicationDispense Category CodesOther1314
medicationdispense-performer-functionMedicationDispense Performer Function CodesOther1318
medicationdispense-statusMedicationDispense Status CodesOther1312
medicationdispense-status-reasonMedicationDispense Status CodesOther1316
medicationknowledge-characteristicMedicationKnowledge Characteristic CodesOther1337
medicationknowledge-package-typeMedicationKnowledge Package Type CodesOther1339
medicationknowledge-statusMedicationKnowledge Status CodesOther1335
medicationrequest-categoryMedicationRequest Category CodesOther1322
medicationrequest-course-of-therapyMedicationRequest Course of Therapy CodesOther1326
medicationrequest-intentMedicationRequest Status CodesInternal1321
medicationrequest-statusMedicationRequest Status CodesInternal1320
medicationrequest-status-reasonMedicationRequest Status Reason CodesOther1324
message-events NOne of the message events defined as part of this version of FHIR.Internal26
message-reason-encounterExample Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.Other378
message-significance-categoryThe impact of the content of a message.Internal188
message-transport NThe protocol used for message transport.Other184
messageheader-response-requestHL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.Internal924
metric-calibration-stateDescribes the state of a metric calibration.Internal652
metric-calibration-typeDescribes the type of a metric calibration.Internal650
metric-categoryDescribes the category of the metric.Internal648
metric-colorDescribes the typical color of representation.Internal654
metric-operational-statusDescribes the operational status of the DeviceMetric.Internal646
mimetypes NThis value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13)Other1024
missing-tooth-reasonThis value set includes sample Missing Tooth Reason codes.Other534
modified-foodtypeTextureModifiedFoodType: 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 CT388
name-assembly-orderA code that represents the preferred display order of the components of a human name.Other, V2, V3913
name-part-qualifierA set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type.V3906
name-use NThe use of a human name.Internal65
name-v3-representationA set of codes for each different representation of a name.V3909
namingsystem-identifier-typeIdentifies the style of unique identifier used to identify a namespace.Internal492
namingsystem-typeIdentifies the purpose of the naming system.Internal490
narrative-statusThe status of a resource narrative.Internal55
network-typeThe type of network access point of this agent in the audit event.Internal456
nhin-purposeofuseThis 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.Othernull
note-typeThe presentation types of notes.Internal15
nutrient-codeNutrientModifier : Codes for types of nutrients that are being modified such as carbohydrate or sodium. This value set includes codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 226355009 (Nutrients(substance)), and the concepts for Sodium, Potassium and Fluid. This is provided as a suggestive example.SNOMED CT386
object-lifecycle-eventsThis example FHIR value set is comprised of lifecycle event codes. The FHIR Actor value set is based on DICOM Audit Message, ParticipantObjectDataLifeCycle; ISO Standard, TS 21089-2017; Othernull
object-roleCode representing the role the entity played in the audit event.Other460
observation-categoryObservation Category codes.Other403
observation-codesThis value set includes all LOINC codesLOINC396
observation-interpretation NA categorical assessment, providing a rough qualitative interpretation of the observation value, such as “normal”/ “abnormal”,”low” / “high”, “better” / “worse”, “susceptible” / “resistant”, “expected”/ “not expected”. The value set is intended to be for ANY use where coded representation of an interpretation is needed. Notes: This is being communicated in v2.x in OBX-8 (Observation Interpretation), in v3 in ObservationInterpretation (CWE) in R1 (Representative Realm) and in FHIR in Observation.interpretation. Historically these values come from the laboratory domain, and these codes are extensively used. The value set binding is extensible, so codes outside the value set that are needed for interpretation concepts (i.e. particular meanings) that are not included in the value set can be used, and these new codes may also be added to the value set and published in a future version.V3399
observation-methodsObservation Method codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 272394005 (Technique (qualifier value)) or is-a 129264002 (Action (qualifier value)) or is-a 386053000 (Evaluation procedure(procedure))SNOMED CT395
observation-range-categoryCodes identifying the category of observation range.Internal1333
observation-statisticsThe statistical operation parameter -"statistic" codes.Other405
observation-status NCodes providing the status of an observation.Internal400
observation-vitalsignresultThis value set indicates the allowed vital sign result types. The LOINC code for Vitals Signs panel (85353-1) is a grouping structure for a set of vital signs and includes related links (with type=has-member) to the Observations in this set (e.g. respiratory rate, heart rate, BP). The Blood pressure panel (85354-9) is used to group the component observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4).LOINC62
operation-kind NWhether an operation is a normal operation or a query.Internal506
operation-outcomeOperation Outcome codes used by FHIR test servers (see Implementation file translations.xml)Other412
operation-parameter-use NWhether an operation parameter is an input or an output parameter.Internal508
oral-prosthodontic-materialThis value set includes sample Oral Prosthodontic Material type codes.Internal538
organization-roleThis example value set defines a set of codes that can be used to indicate the role of one Organization in relation to another.Internal880
organization-typeThis example value set defines a set of codes that can be used to indicate a type of organization.Other414
orientation-typeType for orientation.Internal987
parameter-groupCodes identifying groupings of parameters; e.g. Cardiovascular.Other632
parent-relationship-codesThe 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.V3921
participant-roleRoles of Participants that may be included in a CarePlan.Participants, or in an EpisodeOfCare.team. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization (qualifier value).SNOMED CT152
participantrequiredIs the Participant required to attend the appointment.Internal488
participation-role-typeThis FHIR value set is comprised of Actor participation Type codes, which can be used to value FHIR agents, actors, and other role elements. The FHIR Actor participation type value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes.Other, V3, DICOM54
participationstatusThe Participation status of an appointment.Internal486
patient-contactrelationship NThe nature of the relationship between the patient and the contact person.V21130
payeetypeThis value set includes sample Payee Type codes.Other31
payment-adjustment-reasonThis value set includes smattering of Payment Adjustment Reason codes.Other600
payment-statusThis value set includes a sample set of Payment Status codes.Other643
payment-typeThis value set includes sample Payment Type codes.Other641
performer-functionThe types of involvement of the performer in the Event.V3null
performer-roleThis examples value set defines the set of codes that can be used to indicate a role of procedure performer.SNOMED CT433
permitted-data-typePermitted data type for observation value.Internal1331
plan-definition-typeThe type of PlanDefinition.Other797
postal-address-useUses of an address not included in Address.use.V3908
practitioner-roleThis example value set defines a set of codes that can be used to indicate the role of a Practitioner.Other, SNOMED CT439
practitioner-specialtyThis example value set defines a set of codes that can be used to indicate the specialty of a Practitioner.Internal441
precision-estimate-typeMethod of reporting variability of estimates, such as confidence intervals, interquartile range or standard deviation.Other1357
prepare-patient-prior-specimen-collectionChecks on the patient prior specimen collection. All SNOMED CT concepts descendants of 703763000 |Precondition value (qualifier value)|SNOMED CT0
probability-distribution-typeCodes specifying the type of probability distribution.V3907
procedure-categoryProcedure Category code: A selection of relevant SNOMED CT codes.SNOMED CT430
procedure-codeProcedure Code: All SNOMED CT procedure codes.SNOMED CT427
procedure-followupProcedure follow up codes: a selection of SNOMED CT codes relevant to procedure follow up.SNOMED CT429
procedure-not-performed-reasonSituation 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 CT431
procedure-outcomeProcedure Outcome code: A selection of relevant SNOMED CT codes.SNOMED CT428
procedure-progress-status-codesThis value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the procedure performance process.Internal946
procedure-reasonThis examples value set defines the set of codes that can be used to indicate a reasons for a procedure.SNOMED CT432
process-priorityThis value set includes the financial processing priority codes.Other552
product-categoryBiologically Derived Product Category.Internal900
product-statusBiologically Derived Product Status.Internal902
product-storage-scaleBiologicallyDerived Product Storage Scale.Internal904
programThis value set defines an example set of codes that could be can be used to classify groupings of service-types/specialties.Other0
property-representation NHow a property is represented when serialized.Internal87
provenance-activity-typeThis value set contains representative Activity Type codes, which includes codes from the HL7 DocumentCompletion, ActStatus, and DataOperations code system, W3C PROV-DM and PROV-N concepts and display names, several HL7 Lifecycle Event codes for which there are agreed upon definitions, and non-duplicated codes from the HL7 Security and Privacy Ontology Operations codes.V3438
provenance-agent-roleThe role that a provenance participant playedInternal1305
provenance-agent-typeThe type of participation a provenance participant.Other1003
provenance-entity-roleHow an entity was used in an activity.Internal436
provenance-history-agent-typeTypes of roles indicating how a particular agent was involved with the creation or modification of a resource for use when exposing event historyV3927
provenance-history-record-activityCodes for Provenance activities that are relevant when capturing event history for resources.V3926
provider-qualificationThis value set includes sample Provider Qualification codes.Other570
provider-taxonomyNUCC Healthcare Provider Taxonomy codesOther51
publication-status NThe lifecycle status of an artifact.Internal3
quality-typeType for quality report.Internal228
quantity-comparator NHow the Quantity should be understood and represented.Internal59
question-max-occursFlags an element as having unlimited repetitions.Other929
questionnaire-answersExample list of codes for answers to questions. (Not complete or necessarily appropriate.)SNOMED CT446
questionnaire-answers-statusLifecycle status of the questionnaire response.Internalrequired
questionnaire-categoryExample list of potential categories for questionnaires.SNOMED CT928
questionnaire-display-categoryCodes defining the purpose of a Questionnaire item of type 'text'.Internal935
questionnaire-enable-behaviorControls how multiple enableWhen values are interpreted - whether all or any must be true.Internal1007
questionnaire-enable-operatorThe criteria by which a question is enabled.Internal1005
questionnaire-item-controlStarter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire.Internal931
questionnaire-questionsExample list of codes for questions and groups of questions. (Not necessarily complete or appropriate.)LOINC443
questionnaire-usage-modeIdentifies the modes of usage of a questionnaire that should enable a particular questionnaire item.Other937
questionnaireresponse-modeCodes describing how the QuestionnaireResponse was populatedV31290
reaction-event-certaintyStatement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event.Other942
reaction-event-severityClinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.Internal135
reason-medication-given-codesThis value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process.Other344
reason-medication-not-given-codesThis 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 CT342
reason-medication-status-codesThis value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplarSNOMED CT369
recommendation-strengthA rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems.Other1021
ref-sequencesREFSEQ : National Center for Biotechnology Information (NCBI) Reference SequencesOther280
reference-handling-policy NA set of flags that defines how references are supported.Internal202
reference-version-rules NWhether a reference needs to be version specific or version independent, or whether either can be used.Internal89
referencerange-appliestoThis value set defines a set of codes that can be used to indicate the particular target population the reference range applies to.Other, SNOMED CT407
referencerange-meaningThis value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population.Other397
rejection-criteriaCriterion for rejection of the specimen by laboratory.Other856
related-artifact-typeThe type of relationship to the related artifact.Internal99
related-claim-relationshipThis value set includes sample Related Claim Relationship codes.Other568
relatedperson-relationshiptypeA set of codes that can be used to indicate the relationship between a Patient and a Related Person.V2, V3449
relation-typeThe type of relations between entries.Internal1028
relationshipThis value set includes the Patient to subscriber relationship codes.Internal35
remittance-outcomeThis value set includes Claim Processing Outcome codes.Internal13
report-action-result-codesThe results of executing an action.Internal720
report-codesThis value set includes LOINC codes that relate to Diagnostic Observations.LOINC233
report-participant-typeThe type of participant.Internal722
report-result-codesThe reported execution result.Internal718
report-status-codesThe current status of the test report.Internal724
repository-typeType for access of external URI.Internal230
request-intentCodes indicating the degree of authority/intentionality associated with a request.Internal113
request-priorityThe clinical priority of a diagnostic order.Internal115
request-resource-typesA list of all the request resource types defined in this version of the FHIR specification.Internal1058
request-statusCodes identifying the lifecycle stage of a request.Internal111
research-element-typeThe possible types of research elements (E.g. Population, Exposure, Outcome).Internal1341
research-study-objective-typeCodes for the kind of study objective.Other823
research-study-phaseCodes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation.Other821
research-study-prim-purp-typeCodes for the main intent of the study.Other827
research-study-reason-stoppedCodes for why the study ended prematurely.Other825
research-study-statusCodes that convey the current status of the research study.Internal819
research-subject-statusIndicates the progression of a study subject through a study.Internal829
resource-aggregation-mode NHow resource references can be aggregated.Internal85
resource-security-categoryProvides general guidance around the kind of access Control to Read, Search, Create, Update, or Delete a resource.Other0
resource-slicing-rules NHow slices are interpreted when evaluating an instance.Internal83
resource-statusThe master set of status codes used throughout FHIR. All status codes are mapped to one of these codes.Internal117
resource-type-linkThe type of payee Resource.Other614
resource-types NOne of the resource types defined as part of this version of FHIR.Internal27
resource-validation-modeCodes indicating the type of validation to perform.Internal118
response-codeThe kind of response to a message.Internal380
restful-capability-mode NThe mode of a RESTful capability statement.Internal176
restful-security-service NTypes of security services used with FHIR.Other178
risk-estimate-typeWhether the risk estimate is dichotomous, continuous or qualitative and the specific type of risk estimate (eg proportion or median).Other1363
risk-probabilityCodes representing the likelihood of a particular outcome in a risk assessment.Other450
route-codesThis value set includes all Route codes from SNOMED CT - provided as an exemplar.SNOMED CT98
search-comparatorWhat Search Comparator Codes are supported in search.Internal637
search-entry-mode NWhy an entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process.Internal622
search-modifier-codeA supported modifier for a search parameter.Internal639
search-param-type NData types allowed to be used for search parameters.Internal11
search-xpath-usageHow a search parameter relates to the set of elements returned by evaluating its xpath query.Internal635
secondary-findingCodes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding.Internal1285
security-labels NA single value set for all security labels defined by FHIR.Other47
security-role-typeThis example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user's access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient.Other, V3, DICOM978
sequence-quality-methodThis value set includes sequence quality methodOther223
sequence-quality-standardSequenceThis value set includes sequence quality standardOther222
sequence-referenceSeqThis value set includes all Reference codesOther221
sequence-speciesCodes 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 exampleSNOMED CT216
sequence-typeType if a sequence -- DNA, RNA, or amino acid sequence.Internal219
sequenceontologySequence OntologyOther1044
series-performer-functionPerformer function of an agent in an imaging study seriesV3989
service-categoryThis value set defines an example set of codes that can be used to classify groupings of service-types/specialties.Other516
service-modifiersThis value set includes sample Service Modifier codes.Internal572
service-pharmacyThis value set includes a smattering of Pharmacy Service codes.Internal562
service-placeThis value set includes a smattering of Service Place codes.Other564
service-productThis value set includes a smattering of Service/Product codes.Internal560
service-provision-conditionsThe code(s) that detail the conditions under which the healthcare service is available/offered.Other514
service-referral-methodThe methods of referral can be used when referring to a specific HealthCareService resource.Other510
service-typeThis value set defines an example set of codes of service-types.Other518
service-usclsThis value set includes a smattering of USCLS codes.Other542
servicerequest-categoryAn example value set of SNOMED CT concepts that can classify a requested serviceSNOMED CT434
servicerequest-orderdetailAn example value set of Codified order entry details concepts. These concepts only make sense in the context of what is being ordered. This example is for a patient ventilation orderSNOMED CT435
sibling-relationship-codesThe value set includes the v3 RoleCode SIB (sibling) and all of its specializations. It covers the relationships needed to establish genetic pedigree relationships between family members.V3922
signature-typeThe 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.Other12
slotstatusThe free/busy status of the slot.Internal482
smart-capabilitiesCodes that define what the server is capable of.Other1018
sort-directionThe possible sort directions, ascending or descending.Internal979
spdx-licenseThe license that applies to an Implementation Guide (using an SPDX license Identifiers, or 'not-open-source'). The binding is required but new SPDX license Identifiers are allowed to be used (https://spdx.org/licenses/).Internal1026
special-valuesA set of generally useful codes defined so they can be included in value sets.Other9
specimen-collectionActions that can be taken for the collection of specimen from a subject.SNOMED CT0
specimen-collection-method This example value set defines a set of codes that can be used to indicate the method by which a specimen was collected.SNOMED CT468
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.Other939
specimen-contained-preferenceDegree of preference of a type of conditioned specimen.Internal852
specimen-container-typeChecks on the patient prior specimen collection. All SNOMED CT concepts descendants of 706041008 |Device for body fluid and tissue collection/transfer/processing (physical object)|SNOMED CT470
specimen-processing-procedureThe technique that is used to perform the process or preserve the specimen.V2469
specimen-statusCodes providing the status/availability of a specimen.Internal471
standards-statusHL7 Ballot/Standards status of artifact.Other1365
strand-typeType for strand.Internal985
structure-definition-kind NDefines the type of structure that a definition is describing.Internal668
study-typeTypes of research studies (types of research methods).Other1349
subject-typePossible types of subjects.Internal775
subscriber-relationshipThis value set includes codes for the relationship between the Subscriber and the Beneficiary (insured/covered party/patient).Other0
subscription-channel-typeThe type of method used to execute a subscription.Internal500
subscription-statusThe status of a subscription.Internal502
subscription-tagTags to put on a resource after subscriptions have been sent.Other504
substance-categorySubstance category codesOther476
substance-codeThis value set contains concept codes for specific substances. It includes codes from [SNOMED](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) and where concept is-a 373873005 (Pharmaceutical / biologic product (product))SNOMED CT473
substance-statusA code to indicate if the substance is actively used.Internal474
supplement-typeSupplementType : Codes for nutritional supplements to be provided to the patient. This value set is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example.SNOMED CT390
supply-itemThis value set includes [SNOMED CT](http://snomed.info/sct) where concept is-a 105590001 (Substance (substance)) or concept is-a 260787004 (Physical object) and provided as an example value set.SNOMED CT699
supplydelivery-statusStatus of the supply delivery.Internal700
supplydelivery-typeThis value sets refers to a specific supply item.Other702
supplyrequest-kindThis value sets refers to a Category of supply.Other693
supplyrequest-reasonThe reason why the supply item was requested.Other697
supplyrequest-statusStatus of the supply request.Internal695
surfaceThis value set includes a smattering of FDI tooth surface codes.Other546
synthesis-typeTypes of combining results from a body of evidence (eg. summary data meta-analysis).Other1347
system-restful-interaction NOperations supported by REST at the system level.Internal181
task-intentDistinguishes whether the task is a proposal, plan or full order.Internal1240
task-statusThe current status of the task.Internal790
teethThis value set includes the FDI Teeth codes.Internal550
template-status-codeThe status indicates the level of maturity of the design and may be used to manage the use of the design.Other8
testscript-operation-codesThis value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.Other704
testscript-profile-destination-typesThis 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.Other714
testscript-profile-origin-typesThis 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.Other712
texture-codeTextureModifier: 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 CT387
timezonesIANA Timezone CodesOther1036
timing-abbreviationCode for a known / defined timing pattern.V378
toothThis value set includes a smattering of FDI oral site codes.Other540
transaction-modeA code that indicates how transactions are supported.Internal192
trigger-typeThe type of trigger.Internal103
type-derivation-rule NHow a type relates to its baseDefinition.Internal673
type-restful-interaction NOperations supported by REST at the type or instance level.Internal180
ucum-bodylengthUCUM units for recording body length measures such as height and head circumferenceFHIR958
ucum-bodytempUCUM units for recording Body TemperatureFHIR957
ucum-bodyweightUCUM units for recording Body WeightFHIR956
ucum-commonCommonly encountered UCUM units (for purposes of helping populate look ups.FHIRnull
ucum-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR912
ucum-vitals-commonCommon UCUM units for recording Vital SignsFHIR955
udiThis value set includes sample UDI codes.Internal554
udi-entry-typeCodes to identify how UDI data was entered.Internal211
units-of-time NA unit of time (units from UCUM).FHIR77
unknown-content-codeA code that indicates whether an application accepts unknown elements or extensions when reading resources.Internal196
usage-context-typeA code that specifies a type of context being specified by a usage context.Other101
use-contextThis value set defines a base set of codes that can be used to indicate that the content in a resource was developed with a focus and intent of supporting use within particular contexts.Other, SNOMED CT28
vaccine-codeThis identifies the vaccine substance administered - CVX codes.Internal, Other22
variable-typeThe possible types of variables for exposures or outcomes (E.g. Dichotomous, Continuous, Descriptive).Internal1343
variant-stateCodes providing the status of the variant test result.Other217
variantsHGVS : Human Genome Variation SocietyOther282
verificationresult-can-push-updatesAbility of the primary source to push updates/alertsOther896
verificationresult-communication-methodAttested information may be validated by process that are manual or automated. For automated processes it may accomplished by the system of record reaching out through another system's API or information may be sent to the system of record. This value set defines a set of codes to describing the process, the how, a resource or data element is validated.Other0
verificationresult-failure-actionThe result if validation failsOther890
verificationresult-needThe frequency with which the target must be validatedOther882
verificationresult-primary-source-typeType of the validation primary sourceOther892
verificationresult-push-type-availableType of alerts/updates the primary source can sendOther898
verificationresult-statusThe validation status of the targetInternal884
verificationresult-validation-processThe primary process by which the target is validatedOther888
verificationresult-validation-statusStatus of the validation of the target against the primary sourceOther894
verificationresult-validation-typeWhat the target is validated againstOther886
versioning-policy NHow the system supports versioning for a resource.Internal190
vision-base-codesA coded concept listing the base codes.Internal662
vision-eye-codesA coded concept listing the eye codes.Internal660
vision-productThis value set includes a smattering of Prescription Product codes.Other658
written-languageThis value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47) for the purpose of writing; this value set (unlike the common languages value set) doesn't include dialects except where they are relevant for written languagesOthernull
yesnodontknowFor Capturing simple yes-no-don't know answersOthernull
Namespace: http://dicom.nema.org/medical/dicom/current/output/chtml/part16
sect_CID_29.html Transitive closure of CID 29 AcquisitionModalityDICOM19
sect_CID_29.html|20121129 Transitive closure of CID 29 AcquisitionModalityDICOM19
Name (URI = http://terminology.hl7.org/ValueSet/v3-...) NameOID
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 correctness2.16.840.1.113883.1.11.155
AcknowledgementDetailCode OpenIssue: Missing description.--
AcknowledgementDetailType A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'2.16.840.1.113883.1.11.19358
AcknowledgementType This attribute contains an acknowledgement code as described in the HL7 message processing rules. OpenIssue: Description was copied from attribute and needs to be improved to be appropriate for a code system.2.16.840.1.113883.1.11.8
ActClass**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.11527
ActClassClinicalDocument A clinical document is a documentation of clinical observations and services, with the following characteristics: (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care; (3) Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; (5) Human readability - A clinical document is human readable."2.16.840.1.113883.1.11.13948
ActClassDocument Specialization of Act to add the characteristics unique to document management services.2.16.840.1.113883.1.11.18938
ActClassInvestigation An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government.2.16.840.1.113883.1.11.20224
ActClassObservation Description: An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. Thecode attribute of Observation and thevalue attribute of Observation must be considered in combination to determine the semantics of the observation. Discussion: Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. Examples: Recording the results of a Family History Assessment Laboratory test and associated result Physical exam test and associated result Device temperature Soil lead level2.16.840.1.113883.1.11.11529
ActClassProcedure An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Examples: : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc.2.16.840.1.113883.1.11.19665
ActClassROI Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present.2.16.840.1.113883.1.11.17893
ActClassSupply Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.2.16.840.1.113883.1.11.11535
ActCode A code specifying the particular kind of Act that the Act-instance represents within its class. Constraints: The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted.--
ActConsentDirective ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms.2.16.840.1.113883.1.11.20425
ActConsentType Definition: The type of consent directive, e.g., to consent or dissent to collect, access, or use in specific ways within an EHRS or for health information exchange; or to disclose health information for purposes such as research.2.16.840.1.113883.1.11.19897
ActCoverageTypeCode Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties.2.16.840.1.113883.1.11.19855
ActEncounterCode Domain provides codes that qualify the ActEncounterClass (ENC)2.16.840.1.113883.1.11.13955
ActExposureLevelCode A qualitative measure of the degree of exposure to the causative agent. This includes concepts such as "low", "medium" and "high". This quantifies how the quantity that was available to be administered to the target differs from typical or background levels of the substance.--
ActIncidentCode Set of codes indicating the type of incident or accident.2.16.840.1.113883.1.11.16508
ActInvoiceElementModifier Processing consideration and clarification codes.2.16.840.1.113883.1.11.17704
ActInvoiceGroupCode Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements.2.16.840.1.113883.1.11.19398
ActMood OpenIssue: In Ballot 2009May, a strong Negative vote was lodged against several of the concept definitions in the vocabulary used for Act.moodCode. The vote was found "Persuasive With Mod", with the understanding that M and M would undertake a detailed review of these concept definitions for a future release of the RIM.2.16.840.1.113883.1.11.10196
ActMoodIntent An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order.2.16.840.1.113883.1.11.10199
ActMoodPredicate Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events.2.16.840.1.113883.1.11.10202
ActPharmacySupplyType Identifies types of dispensing events2.16.840.1.113883.1.11.16208
ActPriority A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.--
ActReason A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".--
ActRelationshipCheckpoint**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10349
ActRelationshipConditional Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred2.16.840.1.113883.1.11.18977
ActRelationshipFulfills The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act.2.16.840.1.113883.1.11.10342
ActRelationshipHasComponent A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently.2.16.840.1.113883.1.11.10318
ActRelationshipJoin**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10360
ActRelationshipPertains This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays.2.16.840.1.113883.1.11.10329
ActRelationshipSplit**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10355
ActRelationshipSubset <ns1:p>Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.</ns1:p><ns1:p>Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.</ns1:p>2.16.840.1.113883.1.11.19613
ActRelationshipType The source is an excerpt from the target.2.16.840.1.113883.1.11.10317
ActSite An anatomical location on an organism which can be the focus of an act.--
ActStatus Codes representing the defined possible states of an Act, as defined by the Act class state machine.2.16.840.1.113883.1.11.15933
ActSubstanceAdminSubstitutionCodeNo Description Provided2.16.840.1.113883.1.11.16621
ActTaskCode Description: A task or action that a user may perform in a clinical information system.2.16.840.1.113883.1.11.19846
ActUSPrivacyLaw A jurisdictional mandate in the US relating to privacy. Deprecation Comment: Content moved to ActCode under _ActPrivacyLaw; use that instead.--
ActUncertainty OpenIssue: Missing Description2.16.840.1.113883.1.11.16899
AddressPartType Description: Code that specifies whether an address part names the street, city, country, postal code, post box, etc. Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"2.16.840.1.113883.1.11.10642
AddressUse Codes that provide guidance around the circumstances in which a given address should be used.2.16.840.1.113883.1.11.190
AdministrativeGender The gender of a person used for adminstrative purposes (as opposed to clinical gender)2.16.840.1.113883.1.11.1
AmericanIndianAlaskaNativeLanguages American Indian and Alaska Native languages currently being used in the United States.--
Calendar**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.17422
CalendarCycle Calendar cycle identifiers--
CalendarType**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10682
Charset Internet Assigned Numbers Authority (IANA) Charset Types2.16.840.1.113883.1.11.14853
CodingRationale Identifies how to interpret the instance of the code, codeSystem value in a set of translations. Since HL7 (or a government body) may mandate that codes from certain code systems be sent in conformant messages, other synonyms that are sent in the translation set need to be distinguished among the originally captured source, the HL7 specified code, or some future role. When this code is NULL, it indicates that the translation is an undefined type. When valued, this property must contain one of the following values: SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination) There may be additional values added to this value set as we work through the use of codes in messages and determine other Use Cases requiring special interpretation of the translations.2.16.840.1.113883.1.11.19250
CommunicationFunctionType Describes the type of communication function that the associated entity plays in the associated transmission.2.16.840.1.113883.1.11.16031
Compartment A named tag set for metadata used to populate a security category label field that "segments" an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System) Usage Note: This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk."2.16.840.1.113883.1.11.20478
CompressionAlgorithm**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10620
Confidentiality A set of codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality".--
ConfidentialityClassification Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality".2.16.840.1.113883.1.11.10228
ContainerCap The type of cap associated with a container--
ContainerSeparator A material in a blood collection container that facilites the separation of of blood cells from serum or plasma2.16.840.1.113883.1.11.14054
ContentProcessingMode Description: Identifies the order in which content should be processed.2.16.840.1.113883.1.11.19823
ContextControl A code that specifies how an ActRelationship or Participation contributes to the context of an Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see also attributes Participation.contextControlCode, ActRelationship.contextControlCode, ActRelationship.contextConductionInd).2.16.840.1.113883.1.11.16478
DataOperation**** MISSING DEFINITIONS ****--
Dentition**** MISSING DEFINITIONS ****--
DeviceAlertLevel Domain values for the Device.Alert_levelCode2.16.840.1.113883.1.11.14066
DocumentCompletion Identifies the current completion state of a clinical document.2.16.840.1.113883.1.11.271
DocumentSectionType The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc.2.16.840.1.113883.1.11.10871
DocumentStorage Identifies the storage status of a document.--
EducationLevel Years of education that a person has completed2.16.840.1.113883.1.11.19175
EmployeeJobClass**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.16036
EncounterAdmissionSource**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.12234
EncounterSpecialCourtesy**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.12242
EntityClass Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing.2.16.840.1.113883.1.11.10882
EntityClassDevice A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind of device is identified by the code attribute inherited from Entity. Usage: This includes durable (reusable) medical equipment as well as disposable equipment.2.16.840.1.113883.1.11.11623
EntityClassLivingSubject Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject.)2.16.840.1.113883.1.11.10884
EntityClassManufacturedMaterial Corresponds to the ManufacturedMaterial class2.16.840.1.113883.1.11.13934
EntityClassOrganization A social or legal structure formed by human beings.2.16.840.1.113883.1.11.10889
EntityClassPlace A physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant.2.16.840.1.113883.1.11.10892
EntityClassRoot Corresponds to the Entity class2.16.840.1.113883.1.11.13922
EntityCode OpenIssue: Missing description.--
EntityDeterminer EntityDeterminer in natural language grammar is the class of words that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing.2.16.840.1.113883.1.11.10878
EntityDeterminerDetermined The described determiner is used to indicate that the given Entity is taken as a general description of a kind of thing that can be taken in whole, in part, or in multiples.2.16.840.1.113883.1.11.10879
EntityHandling**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.13988
EntityNamePartQualifier OpenIssue: Needs description2.16.840.1.113883.1.11.15888
EntityNamePartQualifierR2 Description: The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records.2.16.840.1.113883.1.11.20323
EntityNamePartType**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.15880
EntityNamePartTypeR2 Description: Indicates whether the name part is a given name, family name, prefix, suffix, etc.2.16.840.1.113883.1.11.20322
EntityNameUse**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.15913
EntityNameUseR2 Description: A set of codes advising a system or user which name in a set of names to select for a given purpose.2.16.840.1.113883.1.11.20321
EntityRisk Kinds of risks associated with the handling of the material..--
EntityStatus Codes representing the defined possible states of an Entity, as defined by the Entity class state machine.2.16.840.1.113883.1.11.16005
EquipmentAlertLevel**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10896
Ethnicity In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both.--
ExposureMode Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.--
FamilyMember A relationship between two people characterizing their "familial" relationship2.16.840.1.113883.1.11.19579
GTSAbbreviation Open Issue: It appears that the printnames are suboptimal and should be improved for many of the existing codes.--
GenderStatus**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.11523
GeneralPurposeOfUse Supports communication of purpose of use at a general level.2.16.840.1.113883.1.11.20449
HL7ContextConductionStyleThe styles of context conduction usable by relationships within a static model derived from tyhe HL7 Reference Information Model.2.16.840.1.113883.1.11.20380
HL7StandardVersionCode This code system holds version codes for the Version 3 standards. Values are to be determined by HL7 and added with each new version of the HL7 Standard.2.16.840.1.113883.1.11.19373
HL7UpdateMode The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.2.16.840.1.113883.1.11.10018
HtmlLinkType HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the current document and the anchor that is the target of the link2.16.840.1.113883.1.11.11017
HumanLanguage Codes for the representation of the names of human languages.2.16.840.1.113883.1.11.11526
IdentifierReliability Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.2.16.840.1.113883.1.11.20277
IdentifierScope Description: Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II.2.16.840.1.113883.1.11.20276
InformationSensitivityPolicy Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an "employee" sensitivity code would make little sense for use outside of a policy domain. "Taboo" would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.title.2.16.840.1.113883.1.11.20428
IntegrityCheckAlgorithm**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.17385
LanguageAbilityMode A value representing the method of expression of the language. Example: Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.1.11.12249
LanguageAbilityProficiency A value representing the level of proficiency in a language. Example: Excellent, good, fair, poor. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.1.11.12199
LivingArrangement A code depicting the living arrangements of a person--
LocalMarkupIgnore Tells a receiver to ignore just the local markup tags (local_markup, local_header, local_attr) when value="markup", or to ignore the local markup tags and all contained content when value="all"2.16.840.1.113883.1.11.10975
LocalRemoteControlState**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10893
ManagedParticipationStatus Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine.2.16.840.1.113883.1.11.15992
MapRelationship The closeness or quality of the mapping between the HL7 concept (as represented by the HL7 concept identifier) and the source coding system. The values are patterned after the similar relationships used in the UMLS Metathesaurus. Because the HL7 coding sy2.16.840.1.113883.1.11.11052
MaritalStatus * * * No description supplied * * * Open Issue: The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency.--
MessageWaitingPriority Indicates that the receiver has messages for the sender OpenIssue: Description does not make sense relative to name of coding system. Must be reviewed and improved.--
MilitaryRoleType Definition: A person playing the role of program eligible under a program based on military status. Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a member of the military meets jurisdictional or program criteria2.16.840.1.113883.1.11.19812
ModifyIndicator**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.395
NullFlavor A collection of codes specifying why a valid value is not present.2.16.840.1.113883.1.11.10609
ObligationPolicy Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Examples: encrypt Usage Note: Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.2.16.840.1.113883.1.11.20445
ObservationCategory High level observation categories for the general type of observation being made. URL: http://hl7-fhir.github.io/valueset-observation-category.html This is an inline code system http://hl7.org/fhir/observation-category.2.16.840.1.113883.4.642.2.222
ObservationInterpretationOne or more codes providing a rough qualitative interpretation of the observation, such as "normal" / "abnormal", "low" / "high", "better" / "worse", "resistant" / "susceptible", "expected" / "not expected". The value set is intended to be for ANY use where coded representation of an interpretation is needed.2.16.840.1.113883.1.11.78
ObservationMethod A code that provides additional detail about the means or technique used to ascertain the observation. Examples: Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved.2.16.840.1.113883.1.11.20423
ObservationType Identifies the kinds of observations that can be performed2.16.840.1.113883.1.11.16226
ObservationValue This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type. OpenIssue: Description copied from Concept Domain of same name. Must be corrected..--
ParticipationFunction This code is used to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE).2.16.840.1.113883.1.11.10267
ParticipationIndirectTarget Target that is not substantially present in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the act.2.16.840.1.113883.1.11.19032
ParticipationInformationGenerator Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness).2.16.840.1.113883.1.11.10251
ParticipationInformationTranscriber An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.2.16.840.1.113883.1.11.19676
ParticipationMode A set of codes specifying the modality by which the Entity playing the Role is participating in the Act. Examples: Physically present, over the telephone, written communication. Rationale: Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically. Open Issue: There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies.--
ParticipationPhysicalPerformer A person who actually and principally carries out the action. Need not be the principal responsible actor, e.g. a surgery resident operating under supervision of attending surgeon, and may be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.2.16.840.1.113883.1.11.10248
ParticipationSignature A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed. Examples: A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.)2.16.840.1.113883.1.11.10282
ParticipationTargetDirect Target that is substantially present in the service and which is directly affected by the service action (includes consumed material, devices, etc.).2.16.840.1.113883.1.11.10286
ParticipationTargetLocation The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.)2.16.840.1.113883.1.11.10302
ParticipationTargetSubject The principle target that the service acts on. E.g. the patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects, consumables, and devices used as tools for a service are not subjects. However, a device may be a subject of a maintenance service.2.16.840.1.113883.1.11.19584
ParticipationType**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10901
ParticipationVerifier A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.2.16.840.1.113883.1.11.10259
PatientImportance Patient VIP code2.16.840.1.113883.1.11.19265
PaymentTerms Describes payment terms for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor of an invoice.2.16.840.1.113883.1.11.14908
PersonDisabilityType A code identifying a person's disability.--
PersonalRelationshipRoleType Types of personal relationships between two living subjects. Example: Parent, sibling, unrelated friend, neighbor2.16.840.1.113883.1.11.19563
ProbabilityDistributionType**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10747
ProcessingID Codes used to specify whether a message is part of a production, training, or debugging system.2.16.840.1.113883.1.11.103
ProcessingMode**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.207
ProvenanceEventCurrentState Specifies the state change of a target Act, such as a document or an entry, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".2.16.840.1.113883.1.11.20547
ProvenanceEventCurrentState-AS Specifies the state change of a target Act, using ActStatus codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".2.16.840.1.113883.1.11.20545
ProvenanceEventCurrentState-DC Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".2.16.840.1.113883.1.11.20546
PurposeOfUse Supports communication of purpose of use at a general level.2.16.840.1.113883.1.11.20448
QueryParameterValue The domain of coded values used as parameters within QueryByParameter queries.--
QueryPriority**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.91
QueryRequestLimit Definition: Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application.--
QueryResponse A code classifying the general nature of the response to a given query. Includes whether or not data was found, or whether an error occurred.2.16.840.1.113883.1.11.208
QueryStatusCode A code specifying the state of the Query.2.16.840.1.113883.1.11.18899
Race In the United States, federal standards for classifying data on race determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define race, and they recognize the absence of an anthropological or scientific basis for racial classification. Instead, the federal standards acknowledge that race is a social-political construct in which an individual's own identification with one more race categories is preferred to observer identification. The standards use a variety of features to define five minimum race categories. Among these features are descent from "the original peoples" of a specified region or nation. The minimum race categories are American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. The federal standards stipulate that race data need not be limited to the five minimum categories, but any expansion must be collapsible to those categories.--
RefrainPolicy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Examples: prohibit redisclosure without consent directive2.16.840.1.113883.1.11.20446
RelationalOperator**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.209
RelationshipConjunction**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10365
ReligiousAffiliation Assigment of spiritual faith affiliation--
ResponseLevel Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include2.16.840.1.113883.1.11.14761
ResponseModality Defines the timing and grouping of the response instances. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.1.11.394
ResponseMode Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.2.16.840.1.113883.1.11.19650
RoleClass Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains: RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity. RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity. RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between: RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity. RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into: RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement. Personal relationship which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.1.11.11555
RoleClassAgent An entity (player) that acts or is authorized to act on behalf of another entity (scoper).2.16.840.1.113883.1.11.14006
RoleClassAssociative A general association between two entities that is neither partitive nor ontological.2.16.840.1.113883.1.11.19313
RoleClassManufacturedProduct Scoped by the manufacturer2.16.840.1.113883.1.11.11580
RoleClassMutualRelationship A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children).2.16.840.1.113883.1.11.19316
RoleClassPartitive An association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity with a (generally larger) scoping Entity.2.16.840.1.113883.1.11.10429
RoleClassPassive An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity.2.16.840.1.113883.1.11.19105
RoleClassRelationshipFormal A relationship between two entities that is formally recognized, frequently by a contract or similar agreement.2.16.840.1.113883.1.11.10416
RoleClassRoot Corresponds to the Role class2.16.840.1.113883.1.11.13940
RoleClassServiceDeliveryLocation A role played by a place at which services may be provided.2.16.840.1.113883.1.11.16927
RoleClassSpecimen A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen.2.16.840.1.113883.1.11.11591
RoleCode A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes.--
RoleLinkStatus Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.2.16.840.1.113883.1.11.20413
RoleLinkType**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.11603
RoleStatus Codes representing the defined possible states of an Role, as defined by the Role class state machine.2.16.840.1.113883.1.11.15999
RouteOfAdministration The path the administered medication takes to get into the body or into contact with the body.--
SecurityControlObservationValue Security observation values used to indicate security control metadata. V:SecurityControl is the union of V:SecurityPolicy,V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, purpose of use, dissemination controls and other refrain policies, and obligations to which a custodian or receiver is required to comply.2.16.840.1.113883.1.11.20471
SecurityIntegrityObservationValueNo Description Provided2.16.840.1.113883.1.11.20481
SecurityPolicy Types of security policies that further specify the ActClassPolicy value set. Examples: encrypt prohibit redisclosure without consent directive2.16.840.1.113883.1.11.20444
Sequencing Specifies sequence of sort order.2.16.840.1.113883.1.11.390
ServiceDeliveryLocationRoleType A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered.2.16.840.1.113883.1.11.17660
SetOperator**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.17416
SeverityObservation Potential values for observations of severity.2.16.840.1.113883.1.11.16643
SpecimenType**** MISSING DEFINITIONS ****--
SubstanceAdminSubstitutionReasonNo Description Provided2.16.840.1.113883.1.11.19377
SubstitutionCondition Identifies what sort of change is permitted or has occurred between the item that was ordered/requested and the one that was/will be provided.--
TableCellHorizontalAlign These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.1.11.10981
TableCellScope These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.1.11.11012
TableCellVerticalAlign These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.1.11.10987
TableFrame These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.1.11.10992
TableRules These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.1.11.11002
TargetAwareness**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10310
TelecommunicationCapabilities Description: Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address.2.16.840.1.113883.1.11.20312
TimingEvent**** MISSING DEFINITIONS ****2.16.840.1.113883.1.11.10706
TransmissionRelationshipTypeCode Description: A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in which way.2.16.840.1.113883.1.11.19833
TribalEntityUS INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS--
VaccineManufacturer The manufacturer of a vaccine.2.16.840.1.113883.1.11.227
VerificationMethodNo Description Provided2.16.840.1.113883.1.11.19707
WorkClassificationODH Code system of concepts representing a person's job type as defined by compensation and sector (e.g. paid vs. unpaid, self-employed vs. not self-employed, government vs. private, etc.).2.16.840.1.113883.1.11.20560
WorkScheduleODH Describes an individual's typical arrangement of working hours for an occupation.2.16.840.1.113883.1.11.20561
employmentStatusODH Concepts representing whether a person does or does not currently have a job or is not currently in the labor pool seeking employment.2.16.840.1.113883.1.11.20562
hl7ApprovalStatus Description: Codes for concepts describing the approval level of HL7 artifacts. This code system reflects the concepts expressed in HL7's Governance & Operations Manual (GOM) past and present.--
hl7CMETAttribution**** MISSING DEFINITIONS ****--
hl7ITSType Description: Codes identifying types of HL7 Implementation Technology Specifications--
hl7ITSVersionCode HL7 implementation technology specification versions. These codes will document the ITS type and version for message encoding. The code will appear in the instances based upon rules expressed in the ITS, and do not appear in the abstract message, either as it is presented to received from the ITS.--
hl7PublishingDomain Description: Codes for HL7 publishing domains (specific content area)--
hl7PublishingSection Description: Codes for HL7 publishing sections (major business categories)--
hl7PublishingSubSection Description: Codes for HL7 publishing sub-sections (business sub-categories)--
hl7Realm Description: Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models) and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms. All affiliate realm codes may automatically be used as both binding realms and namespace realms. Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms. (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.) All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm. For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types. It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes. However, tooling does not currently support namepace realm codes greater than 2 characters. Open Issue: The name of the concept property "owningAffiliate" should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code. Open Issue: In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length.2.16.840.1.113883.1.11.20355
hl7V3Conformance Description: Identifies allowed codes for HL7aTMs v3 conformance property.--
hl7VoteResolution Description: Based on concepts for resolutions from HL7 ballot spreadsheet according to HL7's Governance & Operations Manual (GOM).--
orderableDrugForm OpenIssue: Missing description.--
policyHolderRole This vocabulary is defined by Implementation Guide for CDA Release 2 - Level 1 - Care Record Summary (US realm). It describes roles recognized through the issuance of an insurance policy to a policyholder who a relationship with the covered party, such as spouse, child, etc. This vocabulary is essentially an inversion of the role relations of the HL7 CoverageRoleType vocabulary. It provides more detailed roles with respect to the underwriter (the scoping organization) for those participants in the policyholder role for a patient. Open Issue: The code values for this coding system must be extracted from the CDA documentation and brought forward through Harmonization for instantiation in this repository.--
styleType <ns1:p>The style code is used within the CDA/SPL narrative block to give the instance author some control over various aspects of style</ns1:p>--
substanceAdminSubstitution Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.--
triggerEventID Description: This code system contains all HL7 artifacts of type TE (Trigger Event) that are created by HL7 or its affiliates or their designates using the realm namespacing rules approved by HL7. Local implementations who create trigger events outside of these namespacing rules, (e.g. using the ZZ realm code) must register their own code system. The specific list of legal codes can be found by consulting the HL7 publications (editions, ballots, implementation guides, etc.) published by HL7 Inc. and by the various HL7 affiliates and their designates. Codes shall be expressed in upper case, with separator as shown in HL7 publications with no version id. E.g. PORX_TE123456UV.2.16.840.1.113883.1.11.20324
xBasicConfidentialityKind Description: Used to enumerate the typical confidentiality constraints placed upon a clinical document. Usage Note: x_BasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject; or that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject.2.16.840.1.113883.1.11.16926
URI Description OID
URI (all prefixed with http://terminology.hl7.org/CodeSystem/v2-/)IDOID
0001Administrative Sex
0002Marital Status
0003Event Type
0004Patient Class
0005Race
0006ReligionVersion Dependent. Use one of:
0007Admission Type
0008Acknowledgment code
0009Ambulatory Status
0012STOCK LOCATION
0017Transaction Type
0023Admit Source
0027Priority
0033ROUTE
0034SITE ADMINISTERED
0038Order status
0043Condition Code
0048What subject filter
0052Diagnosis Type
0061Check Digit Scheme
0062Event Reason
0063Relationship
0065Specimen Action Code
0066Employment Status
0069Hospital Service
0070Specimen Source Codes
0074Diagnostic Service Section ID
0076Message Type
0078Interpretation Codes
0080Nature of Abnormal Testing
0083Outlier Type
0085Observation Result Status Codes Interpretation
0091Query Priority
0092Re-Admission Indicator
0098Type of Agreement
0100Invocation event
0102Delayed acknowledgment type
0103Processing ID
0104Version ID
0105Source of Comment
0106Query/response format code
0107Deferred response type
0108Query results level
0109Report priority
0116Bed Status
0119Order Control Codes
0121Response Flag
0122Charge Type
0123Result Status
0124Transportation Mode
0125Value Type
0126Quantity Limited Request
0127Allergen Type
0128Allergy Severity
0130Visit User Code
0131Contact Role
0133Procedure Practitioner Identifier Code Type
0135Assignment of Benefits
0136Yes/no Indicator
0137Mail Claim Party
0140Military Service
0141Military Rank/Grade
0142Military Status
0144Eligibility Source
0145Room Type
0146Amount Type
0147Policy Type
0148Money or Percentage Indicator
0149Day Type
0150Certification Patient Type
0153Value Code
0155Accept/Application Acknowledgment Conditions
0156Which date/time qualifier
0157Which date/time status qualifier
0158Date/time selection qualifier
0159Diet Code Specification Type
0160Tray Type
0161Allow Substitution
0162Route of Administration
0163Body Site
0164Administration Device
0165Administration Method
0166RX Component Type
0167Substitution Status
0168Processing Priority
0169Reporting Priority
0170Derived Specimen
0173Coordination of Benefits
0174Nature of Service/Test/Observation
0175Master File Identifier Code
0177Confidentiality Code
0178File Level Event Code
0179Response Level
0180Masterfile Action Code
0181MFN Record-level Error Return
0183Active/Inactive
0185Preferred Method of Contact
0187Provider Billing
0189Ethnic Group
0190Address Type
0191Type of Referenced Data
0193Amount Class
0200Name Type
0201Telecommunication Use Code
0202Telecommunication Equipment Type
0203Identifier Type
0204Organizational Name Type
0205Price Type
0206Segment Action Code
0207Processing Mode
0208Query Response Status
0209Relational Operator
0210Relational Conjunction
0211Alternate Character Sets
0213Purge Status Code
0214Special Program Code
0215Publicity Code
0216Patient Status Code
0217Visit Priority Code
0220Living Arrangement
0223Living Dependency
0224Transport Arranged
0225Escort Required
0227Manufacturers of Vaccines (code=MVX)
0228Diagnosis Classification
0229DRG Payor
0230Procedure Functional Type
0231Student Status
0232- Insurance Company Contact Reason
0234Report Timing
0235Report Source
0236Event Reported To
0237Event Qualification
0238Event Seriousness
0239Event Expected
0240Event Consequence
0241Patient Outcome
0242Primary Observer's Qualification
0243Identity May Be Divulged
0247Status of Evaluation
0248Product Source
0250Relatedness Assessment
0251Action Taken in Response to the Event
0252Causality Observations
0253Indirect Exposure Mechanism
0254Kind of Quantity
0255Duration Categories
0256Time Delay Post Challenge
0257Nature of Challenge
0258Relationship Modifier
0259Modality
0260Patient Location Type
0261Location Equipment
0262Privacy Level
0263Level of Care
0265Specialty Type
0267Days of the Week
0268Override
0269Charge On Indicator
0270Document Type
0271Document Completion Status
0272Document Confidentiality Status
0273Document Availability Status
0275Document Storage Status
0276Appointment reason codes
0277Appointment Type Codes
0278Filler status codes
0279Allow Substitution Codes
0280Referral Priority
0281Referral Type
0282Referral Disposition
0283Referral Status
0284Referral Category
0286Provider Role
0287Problem/Goal Action Code
0290MIME base64 encoding characters
0291Subtype of Referenced Data
0292Vaccines Administered
0294Time Selection Criteria Parameter Class Codes
0298CP Range Type
0299Encoding
0301Universal ID Type
0305Person Location Type
0309Coverage Type
0311Job Status
0315Living Will Code
0316Organ Donor Code
0317Annotations
0321Dispense Method
0322Completion Status
0323Action Code
0324Location Characteristic ID
0325Location Relationship ID
0326Visit Indicator
0329Quantity Method
0330Marketing Basis
0331Facility Type
0332Source Type
0334Disabled Person Code
0335Repeat Pattern
0336Referral Reason
0337Certification Status
0338Practitioner ID Number Type
0339Advanced Beneficiary Notice Code
0344Patient's Relationship to Insured
0350Occurrence Code
0351Occurrence Span
0353CWE statuses
0354Message Structure
0355Primary Key Value Type
0356Alternate Character Set Handling Scheme
0357Message Error Condition Codes
0359Diagnosis Priority
0360Degree/License/CertificateVersion Dependent. Use one of:
0363Assigning Authority
0364Comment Type
0365Equipment State
0366Local/Remote Control State
0367Alert Level
0368Remote Control Command
0369Specimen Role
0370Container Status
0371Additive/Preservative
0372Specimen Component
0373Treatment
0374System Induced Contaminants
0375Artificial Blood
0376Special Handling Code
0377Other Environmental Factors
0383Substance Status
0384Substance Type
0387Command Response
0388Processing Type
0389Analyte Repeat Status
0391Segment GroupVersion Dependent. Use one of:
0392Match Reason
0393Match Algorithms
0394Response Modality
0395Modify Indicator
0396Coding System
0397Sequencing
0398Continuation Style Code
0401Government Reimbursement Program
0402School Type
0403Language Ability
0404Language Proficiency
0406Participant Organization Unit Type
0409Application Change Type
0411Supplemental Service Information Values
0415Transfer Type
0416Procedure DRG Type
0417Tissue Type Code
0418Procedure Priority
0421Severity of Illness Code
0422Triage Code
0423Case Category Code
0424Gestation Category Code
0425Newborn Code
0426Blood Product Code
0427Risk Management Incident Code
0428Incident Type Code
0429Production Class Code
0430Mode of Arrival Code
0431Recreational Drug Use Code
0432Admission Level of Care Code
0433Precaution Code
0434Patient Condition Code
0435Advance Directive Code
0436Sensitivity to Causative Agent Code
0437Alert Device Code
0438Allergy Clinical Status
0440Data Types
0441Immunization Registry Status
0442Location Service Code
0443Provider Role
0444Name Assembly Order
0445Identity Reliability Code
0450Event Type
0455Type of Bill Code
0456Revenue code
0457Overall Claim Disposition Code
0459Reimbursement Action Code
0460Denial or Rejection Code
0465Name/Address Representation
0466Ambulatory Payment Classification Code
0468Payment Adjustment Code
0469Packaging Status Code
0470Reimbursement Type Code
0472TQ Conjunction ID
0473Formulary Status
0474Practitioner Organization Unit Type
0475Charge Type Reason
0477Controlled Substance Schedule
0478Formulary Status
0480Pharmacy Order Types
0482Order Type
0483Authorization Mode
0484Dispense Type
0485Extended Priority Codes
0487Specimen Type
0488Specimen Collection Method
0489Risk Codes
0490Specimen Reject Reason
0491Specimen Quality
0492Specimen Appropriateness
0493Specimen Condition
0494Specimen Child Role
0495Body Site Modifier
0496Consent Type
0497Consent Mode
0498Consent Status
0499Consent Bypass Reason
0500Consent Disclosure Level
0501Consent Non-Disclosure Reason
0502Non-Subject Consenter Reason
0503Sequence/Results Flag
0504Sequence Condition Code
0505Cyclic Entry/Exit Indicator
0506Service Request Relationship
0507Observation Result Handling
0508Blood Product Processing Requirements
0510Blood Product Dispense Status
0511BP Observation Status Codes Interpretation
0513Blood Product Transfusion/Disposition Status
0514Transfusion Adverse Reaction
0516Error Severity
0517Inform Person Code
0518Override Type
0520Message Waiting Priority
0523Computation Type
0524Sequence condition
0527Calendar Alignment
0528Event Related Period
0529Precision
0530Organization, Agency, Department
0532Expanded Yes/no Indicator
0534Notify Clergy Code
0535Signature Code
0536Certificate Status
0538Institution Relationship Type
0540Inactive Reason Code
0544Container Condition
0547Jurisdictional Breadth
0548Signatory's Relationship to Subject
0550Body Parts
0553Invoice Control Code
0554Invoice Reason Codes
0555Invoice Type
0556Benefit Group
0557Payee Type
0558Payee Relationship to Invoice
0559Product/Service Status
0561Product/Services Clarification Codes
0562Processing Consideration Codes
0564Adjustment Category Code
0565Provider Adjustment Reason Code
0566Blood Unit Type
0569Adjustment Action
0570Payment Method Code
0571Invoice Processing Results Status
0572Tax status
0615User Authentication Credential Type Code
0616Address Expiration Reason
0617Address Usage
0618Protection Code
0625Item Status Codes
0634Item Importance Codes
0642Reorder Theory Codes
0651Labor Calculation Type
0653Date Format
0657Device Type
0659Lot Control
0667Device Data State
0669Load Status
0682Device Status
0702Cycle Type
0717Access Restriction Value
0719Access Restriction Reason Code
0725Mood Codes
0728CCL Value
0731DRG Diagnosis Determination Status
0734Grouper Status
0739DRG Status Patient
0742DRG Status Financial Calculation
0749DRG Grouping Status
0755Status Weight At Birth
0757DRG Status Respiration Minutes
0759Status Admission
0761DRG Procedure Determination Status
0763DRG Procedure Relevance
0776Item Status
0778Item Type
0790Approving Regulatory Agency
0793Ruling Act
0806Sterilization Type
0818Package
0834MIME Types
0868Telecommunication Expiration Reason
0871Supply Risk Codes
0881Role Executing Physician
0882Medical Role Executing Physician
0894Side of body
0895Present On Admission (POA) Indicator
0904Security Check Scheme
0905Shipment Status
0906ActPriority
0907Confidentiality
0909Patient Results Release Categorization Scheme
0912Participation
0914Root Cause
0916Relevant Clinicial Information
0917Bolus Type
0918PCA Type
0919Exclusive Test
0920Preferred Specimen/Attribute Status
0921Certification Type Code
0922Certification Category Code
0923Process Interruption
0924Cumulative Dosage Limit UoM
0925Phlebotomy Issue
0926Phlebotomy Status
0927Arm Stick
0933Intended Procedure Type
0935Process Interruption Reason
4000Name/address representation