Current Build

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.

NameDefinitionSourceId
Namespace: http://hl7.org/fhir/ValueSet
abstract-typesA type defined by FHIR that is an abstract typeInternal22
account-statusIndicates whether the account is available to be used.Internal714
account-typeThis examples value set defines the set of codes that can be used to represent the type of an account.V3716
action-cardinality-behaviorDefines behavior for an action or a group for how many times that item may be repeatedInternal790
action-condition-kindDefines the kinds of conditions that can appear on actionsInternal798
action-grouping-behaviorDefines organization behavior of a groupInternal782
action-participant-roleEither a practitioner role or a relationship type.Other779
action-participant-typeThe type of participant for the actionInternal794
action-precheck-behaviorDefines selection frequency behavior for an action or groupInternal788
action-relationship-typeDefines the types of relationships between actionsInternal796
action-required-behaviorDefines requiredness behavior for selecting an action or an action groupInternal786
action-selection-behaviorDefines selection behavior of a groupInternal784
action-typeThe type of action to be performedInternal792
actionlistList of allowable action which this resource can request.Internal675
activity-definition-categoryHigh-level categorization of the type of activityInternal775
additional-instruction-codesThis value set includes all SNOMED CT Additional Dosage Instructions.SNOMED CT88
additionalmaterialsThis value set includes sample additional material type codes.Internal521
address-typeThe type of an address (physical / postal)Internal62
address-useThe use of an addressInternal60
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.Internal588
adjudication-errorThis value set includes a smattering of adjudication codes.Internal38
adjudication-reasonThis value set includes smattering of Adjudication Reason codes.Internal590
administration-method-codesThis value set includes some method codes from SNOMED CT - provided as an exemplarSNOMED CT90
administrative-genderThe gender of a person used for administrative purposes.Internal1
adverse-event-actualityOverall nature of the event, e.g. real or potentialInternal910
adverse-event-categoryOverall categorization of the event, e.g. product related or situationalInternal904
adverse-event-causality-assessTODOInternal815
adverse-event-causality-methodTODOInternal817
adverse-event-outcomeTODO (and should this be required?)Internal809
adverse-event-seriousnessOverall seriousness of this event for the patientInternal811
adverse-event-severityThe severity of the adverse event itself, in direct relation to the subjectInternal906
adverse-event-typeThis value set includes all SNOMED CT Clinical Findings.SNOMED CT808
age-unitsUnified Code for Units of Measure (UCUM). This value set includes all UCUM codesFHIR19
all-languagesThis value set includes all possible codes from BCP-47 (http://tools.ietf.org/html/bcp47)Other20
all-typesEither an abstract type, a resource or a data type.Internal24
allerg-intol-substance-exp-riskThe risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products).Internal857
allergy-clinical-statusThe clinical status of the allergy or intolerance.Internal117
allergy-intolerance-categoryCategory of an identified substance.Internal123
allergy-intolerance-criticalityEstimate of the potential clinical harm, or seriousness, of a reaction to an identified substance.Internal119
allergy-intolerance-typeIdentification of the underlying physiological mechanism for a Reaction Risk.Internal121
allergy-verification-statusAssertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance.Internal115
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 CT127
animal-breedsThis example value set defines a set of codes that can be used to indicate breeds of species.SNOMED CT411
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.Internal407
animal-speciesThis example value set defines a set of codes that can be used to indicate species of animal patients.SNOMED CT409
appointmentstatusThe free/busy status of an appointment.Internal477
approach-site-codesThis value set includes Anatomical Structure codes from SNOMED CT - provided as an exemplar.SNOMED CT336
assert-direction-codesThe type of direction to use for assertion.Internal694
assert-operator-codesThe type of operator to use for assertion.Internal696
assert-response-code-typesThe type of response code to use for assertion.Internal698
audit-entity-typeCode for the entity type involved in the audit event.Internal894
audit-event-actionIndicator for type of action performed during the event that generated the eventInternal445
audit-event-outcomeIndicates whether the event succeeded or failedInternal447
audit-event-sub-typeMore detailed code concerning the type of the audit event - defined by DICOM with some FHIR specific additions.DICOM, Internal457
audit-event-typeEvent Types for Audit Events - defined by DICOM with some FHIR specific additions.DICOM, Internal455
audit-source-typeThe type of process where the audit event originated from.Internal459
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.Internal128
benefit-categoryThis value set includes a smattering of Benefit Category codes.Internal594
benefit-networkThis value set includes a smattering of Network type codes.Internal600
benefit-subcategoryThis value set includes a smattering of Benefit SubCategory codes.Internal596
benefit-termThis value set includes a smattering of Benefit Term codes.Internal604
benefit-typeThis value set includes a smattering of Benefit type codes.Internal598
benefit-unitThis value set includes a smattering of Unit type codes.Internal602
binding-strengthIndication of the degree of conformance expectations associated with a binding.Internal42
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 CT653
bodysite-lateralityLaterality: SNOMED-CT concepts for 'left', 'right', and 'bilateral'SNOMED CT281
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 CT1001
bodystructure-relative-locationSNOMED-CT concepts modifying the anatomic locationSNOMED CT1000
bundle-typeIndicates the purpose of a bundle - how it was intended to be used.Internal612
c80-doc-classcodesThis is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). The Document Class value set is reproduced from HITSP C80 Table 2-144 Document Class Value Set Definition. Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests.LOINC46
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-kindHow a capability statement is intended to be used.Internal188
care-plan-activity-kindResource types defined as part of FHIR that can be represented as in-line definitions of a care plan activity.Internal917
care-plan-activity-outcomeExample codes indicating the outcome of a care plan activity. Note that these are in no way complete and may not even be appropriate for some uses.SNOMED CT140
care-plan-activity-statusIndicates where the activity is at in its overall life cycle.Internal134
care-plan-categoryExample codes indicating the category a care plan falls within. Note that these are in no way complete and may not even be appropriate for some uses.SNOMED CT136
care-plan-intentCodes indicating the degree of authority/intentionality associated with a care planInternal141
care-plan-statusIndicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.Internal130
care-team-categoryIndicates the type of care team.Internal146
care-team-statusIndicates the status of the care team.Internal144
catalogTypeThe type of catalogInternal0
chargeitem-billingcodesExample set of codes that can be used for billing purposesInternal823
chargeitem-statusCodes identifying the stage lifecycle stage of a ChargeItemInternal821
choice-list-orientationDirection in which lists of question options should be displayedInternal850
chromosome-humanChromosome number for humanInternal219
claim-careteamroleThis value set includes sample Claim Care Team Role codes.Internal578
claim-exceptionThis value set includes sample Exception codes.Internal572
claim-informationcategoryThis value set includes sample Information Category codes.Internal574
claim-modifiersThis value set includes sample Modifier type codes.Internal528
claim-subtypeThis value set includes sample Claim SubType codes.Internal558
claim-typeThis value set includes sample Claim Type codes.Internal550
claim-useComplete, proposed, exploratory, otherInternal536
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 CT227
clinical-impression-statusThe workflow state of a clinical impression.Internal149
clinicalimpression-prognosisExample value set clinical impression prognosisSNOMED CT151
codesystem-altcode-kindIndicates the type of use for which the code is definedInternal0
codesystem-content-modeHow much of the content of the code system - the concepts and codes it defines - are represented in a code system resourceInternal765
codesystem-hierarchy-meaningThe meaning of the hierarchy of concepts in a code systemInternal767
common-tagsCommon Tag Codes defined by FHIR projectInternal72
communication-categoryCodes for general categories of communications such as alerts, instruction, etc.Internal162
communication-not-done-reasonCodes for the reason why a communication was not done.Internal164
compartment-typeWhich compartment a compartment definition describesInternal769
composite-measure-scoringThe composite scoring method of the measureInternal757
composition-attestation-modeThe way in which a person authenticated a composition.Internal233
composition-statusThe workflow/clinical status of the composition.Internal236
concept-map-equivalenceThe degree of equivalence between concepts.Internal17
concept-property-typeThe type of a property valueInternal763
conceptmap-unmapped-modeDefines which action to take if there is no match in the group.Internal473
condition-categoryPreferred value set for Condition Categories.Internal153
condition-causeExample value set for Cause of Condition codesSNOMED CT879
condition-clinicalPreferred value set for Condition Clinical Status.Internal155
condition-codeExample value set for Condition/Problem/Diagnosis codesSNOMED CT152
condition-outcomeExample value set for Condition OutcomesSNOMED CT881
condition-predecessorExample value set for Condition Predecessor codesSNOMED CT880
condition-severityPreferred value set for Condition/Diagnosis severity gradingSNOMED CT159
condition-stageExample value set for stages of cancer and other conditionsSNOMED CT161
condition-stage-typeExample value set for the type of stages of cancer and other conditionsSNOMED CT912
condition-stateEnumeration indicating whether the condition is currently active, inactive, or has been resolved.Internal877
condition-ver-statusThe verification status to support or decline the clinical status of the condition or diagnosis.Internal157
conditional-delete-statusA code that indicates how the server supports conditional delete.Internal184
conditional-read-statusA code that indicates how the server supports conditional read.Internal190
conformance-expectationIndicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification.Internal838
consent-actionThis value set includes sample Consent Action codes.Internal737
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)Internal, Other, LOINC735
consent-content-classThis value set includes the FHIR resource types, along with some other important content class codesOther, Internal745
consent-content-codeThis example value set contains all LOINC codeLOINC746
consent-data-meaningHow a resource reference is interpreted when testing consent restrictionsInternal743
consent-provision-typeHow a rule statement is applied, such as adding additional consent or removing consentInternal918
consent-scopeThis value set includes sample Consent Action codes.Internal0
consent-state-codesIndicates the state of the consentInternal739
consistency-typeFluidConsistencyType : Codes used to represent the consistency of fluids and liquids provided to the patient. This value set includes all the [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 CT376
constraint-severitySHALL applications comply with this constraint?Internal74
contact-point-systemTelecommunications form for contact pointInternal64
contact-point-useUse of contact pointInternal66
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.Internal405
container-capColor of the container capInternal926
content-typeThe content or mime type.Internal692
contract-actionThis value set includes sample Contract Action codes.Other727
contract-actorroleThis value set includes sample Contract Actor Role codes.Other729
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.Internal733
contract-data-meaningHow a resource reference is interpreted when evaluating contract offersInternal913
contract-signer-typeThis value set includes sample Contract Signer Type codes.Other725
contract-statusThis value set contract specific codes for status.Internal731
contract-subtypeThis value set includes sample Contract Subtype codes.Internal719
contract-term-subtypeThis value set includes sample Contract Term SubType codes.Internal723
contract-term-typeThis value set includes sample Contract Term Type codes.Internal721
contract-typeThis value set includes sample Contract Type codes.Internal717
contributor-typeThe type of contributorInternal86
copy-number-eventCopy Number EventInternal221
coverage-levelThis value set includes sample Coverage Level codes.Internal517
coverage-selfpayThis value set includes Coverage SelfPay codes.Internal519
coverage-typeThis value set includes Coverage Type codes.Internal, Other514
cpt-allA value set that includes all CPT codesOthernull
data-absent-reasonUsed to specify why the normally expected content of the data element is missing.Internal5
data-typesThe type of an element - one of the FHIR data types.Internal21
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, Other829
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, Other830
days-of-weekThe days of the week.Internal506
defined-typesEither a resource or a data type.Internal23
definition-statusCodes identifying the lifecycle stage of a definitionInternal98
definition-topicHigh-level categorization of the definition, used for searching, sorting, and filteringInternal777
designation-useDetails of how a designation would be usedSNOMED CT259
detectedissue-categoryKinds of issues or contraindications, such as 'drug-drug interaction', 'duplicate therapy', etc.V3194
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.V3195
detectedissue-severityIndicates the potential degree of impact of the identified issue on the patient.Internal196
device-actionExample codes indicating the change that happened to the device during the procedure. Note that these are in no way complete and may not even be appropriate for some uses.SNOMED CT416
device-component-propertyCodes for identifying device properties. This is based upon IEEE/HCD specified codesOther925
device-kindCodes used to identify medical devices. Include codes from SNOMED CT (http://www.snomed.org/) where concept is-a 49062001 (Device) and is provided as a suggestive example.SNOMED CT198
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.Other893
device-statement-statusA coded concept indicating the current status of a the Device UsageInternal203
device-statusThe availability status of the device.Internal199
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.Other895
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.Internal48
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 CT919
diagnostic-report-statusThe status of the diagnostic report as a whole.Internal230
diagnostic-service-sectionsThis value set includes all the codes in HL7 v2 table 0074.V2229
dicm-405-mediatypeMedia Type CodeDICOM458
dicom-cid29This Value Set includes codes that may be used to identify an image or waveform acquisition modality, as used in the ImagingStudy resource, Dicom Attribute Modality (0008,0060) or HL7 v2 Table 0259 (see HL7 v2.6 Chapter 8 Section 8.8.8.47). It generally corresponds to a class of diagnostic equipment, or to a specific acquisition function or technique in a device.DICOM​19
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 nclude codes from [SNOMED CT](http://snomed.info/sct) where concept is-a 182922004 (Dietary regime (regime/therapy)) SNOMED CT372
digital-media-subtypeDetailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it.Other, SNOMED CT, Internal327
digital-media-typeWhether the media is a photo, video, or audioInternal325
discriminator-typeHow an element value is interpreted when discrimination is evaluatedInternal84
doc-classcodesLOINC codes for Document Kind, taken from the LOINC document ontology.LOINC238
doc-section-codesDocument section codes (LOINC codes used in CCDA sections).LOINC232
doc-typecodesFHIR Document Codes - all LOINC codes where scale type = 'DOC'.LOINC235
document-modeWhether the application produces or consumes documents.Internal176
document-reference-statusThe status of the document reference.Internal7
document-relationship-typeThe type of relationship between documents.Internal239
encounter-admit-sourceThis value set defines a set of codes that can be used to indicate from where the patient came in.Internal252
encounter-dietThis value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have.Internal250
encounter-discharge-dispositionThis value set defines a set of codes that can be used to where the patient left the hospital.Internal254
encounter-location-statusThe status of the location.Internal257
encounter-participant-typeThis value set defines a set of codes that can be used to indicate how an individual participates in an encounter.V3, Internal245
encounter-reasonThis examples value set defines the set of codes that can be used to indicate reasons for an encounter.SNOMED CT256
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.Internal248
encounter-special-courtesyThis value set defines a set of codes that can be used to indicate special courtesies provided to the patient.V3247
encounter-statusCurrent state of the encounterInternal241
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.Internal243
endpoint-connection-typeThis is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.Internal491
endpoint-payload-typeThis is an example value set defined by the FHIR project, that could be used to represent possible payload document types.Internal, Other489
endpoint-statusThe status of the endpointInternal487
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.V3381
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.Internal379
entformula-typeEnteralFormulaType : Codes for type of enteral formula to be administered to patient. This value set is is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example.SNOMED CT378
episode-of-care-statusThe status of the episode of care.Internal648
episodeofcare-typeThis example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record.Internal650
event-capability-modeThe mode of a message capability statement.Internal172
event-statusCodes identifying the stage lifecycle stage of a eventInternal100
event-timingReal world event relating to the schedule.Internal, V368
ex-diagnosisrelatedgroupThis value set includes example Diagnosis Related Group codes.Internal580
ex-diagnosistypeThis value set includes example Diagnosis Type codes.Internal582
ex-onsettypeThis value set includes sample Service Modifier codes.Internal570
ex-payee-resource-typeThe type of Claim payee ResourceInternal576
ex-paymenttypeThis value set includes example Payment Type codes.Internal608
ex-program-codeThis value set includes sample Program Reason Span codes.Internal568
ex-revenue-centerThis value set includes sample Revenue Center codes.Internal586
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-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 humanInternal934
explanationofbenefit-statusA code specifying the state of the resource instance.Internal610
expression-languageThe media type of the expression languageInternal921
extension-contextHow an extension context is interpreted.Internal656
feeding-deviceMaterials used or needed to feed the patient.Internal, SNOMED CT0
fhir-versionsA historical list of all published FHIR versions. These are the correct values to be used in CapabilityStatement.fhirVersion and StructureDefinition.fhirVersion across all published versions of the specification. Note that other versions have existed, but have not been retained on the HL7 website as they were not advertised milestones. This value set is labelled extensible because the list of published Internal915
filter-operatorThe kind of operation to perform as a part of a property based filter.Internal471
fips-countyThis value set defines FIPS codes for US counties and county equivalent entities.Other41
flag-categoryExample list of general categories for flagged issues. (Not complete or necessarily appropriate.)Internal112
flag-codeExample list of detail codes for flagged issues. (Not complete or necessarily appropriate.)SNOMED CT114
flag-priorityThis value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority.Internal867
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.Internal110
fm-conditionsThis value set includes sample Conditions codes.Internal548
fm-itemtypeThis value set includes sample Item Type codes.Internal540
fm-statusThis value set includes Status codes.Internal584
focal-subjectExample VS composed from SNOMED CT and HL7 v3 codes for observation targets: donor, fetus, spouse. As use cases are discovered more values may be added.SNOMED CT, V3869
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 CT371
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 http://wiki.hl7.org/index.php?title=CDA_Format_Codes_for_IHE_XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incompleteOther3
formsThis value set includes a sample set of Forms codes.Internal36
fundsreserveThis value set includes sample funds reservation type codes.Internal32
goal-acceptance-statusCodes indicating whether the goal has been accepted by a stakeholderInternal836
goal-categoryExample codes for grouping goals for filtering or presentation.Internal270
goal-priorityIndicates the level of importance associated with reaching or sustaining a goal.Internal268
goal-relationship-typeTypes of relationships between two goalsInternal834
goal-start-eventIdentifies types of events that might trigger the start of a goal.SNOMED CT274
goal-statusIndicates whether the goal has been met and is still being targetedInternal266
goal-status-reasonExample codes indicating the reason for a current status. Note that these are in no way complete and may not even be appropriate for some uses.Internal272
graph-compartment-ruleHow a compartment must be linkedInternal275
graph-compartment-useDefines how a compartment rule is usedInternal923
group-typeTypes of resources that are part of groupInternal277
guidance-response-statusThe status of a guidance responseInternal800
guide-dependency-typeHow a dependency is represented when the guide is published.Internal301
guide-page-kindThe kind of an included page.Internal303
handling-conditionSet of handling instructions prior testing of the specimenInternal930
history-absent-reasonCodes describing the reason why a family member's history is not available.Internal908
history-statusA code that identifies the status of the family history record.Internal262
hl7-work-groupAn HL7 administrative unit that owns artifacts in the FHIR specificationInternal861
http-operationsThe allowable request method or HTTP operation codes.Internal704
http-verbHTTP verbs (in the HTTP command line).Internal616
icd-10This value set includes sample ICD-10 codes.Internal523
icd-10-proceduresThis value set includes sample ICD-10 Procedure codes.Internal566
identifier-typeA coded type for an identifier that can be used to determine which identifier to use for a specific purpose.V2, Internal44
identifier-useIdentifies the purpose for this identifier, if known .Internal52
identity-assuranceLevelThe level of confidence that this link represents the same actual person, based on NIST Authentication Levels.Internal640
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.Internal293
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 CT285
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.LOINC298
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.Internal296
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 CT300
immunization-roleThe 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 role a practitioner may play in the immunization event. This value set is provided as a suggestive example.V2295
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.V3284
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.V3283
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.Internal292
implant-statusA set codes that define the functional status of an implanted device.Internal865
inactiveHL7 v3 ActMood Prdicate codes, including inactive codesV3null
instance-availabilityAvailability of the resourceDICOM279
interventionThis value set includes sample Intervention codes.Internal524
investigation-setsExample value set for investigation typeSNOMED CT148
issue-severityHow the issue affects the success of the action.Internal397
issue-typeA code that describes the type of issue.Internal399
item-typeDistinguishes groups from questions and display text and indicates data type for questionsInternal437
jurisdictionThis value set defines a base set of codes for country and region, for indicating where a resource is intended to be usedOther47
kos-titleThe document title code of key object selectionDICOM282
languagesThis value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)Other891
ldlcholesterol-codesLDL Cholesterol codes - measured or calculatedLOINC874
library-typeThe type of knowledge asset this library containsInternal747
link-typeThe type of link between this patient resource and another patient resource.Internal412
linkage-typeUsed to distinguish different roles a resource can play within a set of linked resourcesInternal305
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).Internal313
list-example-codesExample use codes for the List resource - typical kinds of use.Internal307
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.Other311
list-modeThe processing mode that applies to this listInternal309
list-orderBase values for the order of the items in a list resource.Internal315
list-statusThe current state of the listInternal317
location-modeIndicates whether a resource instance represents a specific location or a class of locations.Internal321
location-physical-typeThis example value set defines a set of codes that can be used to indicate the physical form of the Location.Internal319
location-statusIndicates whether the location is still in use.Internal323
manifestation-or-symptomExample value set for Manifestation and Symptom codes.SNOMED CT160
map-context-typeHow to interpret the contextInternal665
map-group-type-modeIf this is the default rule set to apply for the source type, or this combination of typesInternal673
map-input-modeMode for this instance of dataInternal663
map-model-modeHow the referenced structure is used in this mappingInternal661
map-source-list-modeIf field is a list, how to manage the sourceInternal669
map-target-list-modeIf field is a list, how to manage the productionInternal671
map-transformHow data is copied/createdInternal667
marital-statusThis value set defines the set of codes that can be used to indicate the marital status of a person.V328
match-gradeA Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not.Internal882
measure-data-usageThe intended usage for supplemental data elements in the measureInternal755
measure-populationThe type of populationInternal749
measure-report-statusThe status of the measure reportInternal759
measure-report-typeThe type of the measure reportInternal761
measure-scoringThe scoring type of the measureInternal751
measure-typeThe type of measure (includes codes from 2.16.840.1.113883.1.11.20368)Internal753
measurement-principleDifferent measurement principle supported by the device.Internal618
med-admin-perform-functionA code describing the role an individual played in administering the medicationInternal0
med-dispense-perform-functionA code describing the role an individual played in dispensing a medicationInternal0
med-dispense-status-reasonA code describing why a dispense was not performedInternal0
med-request-status-reasonIdentifies the reasons for a given statusInternal0
media-viewCodes defined in SNOMED CT that can be used to record Media Recording views.SNOMED CT329
medication-admin-categoryA coded concept describing where the medication administered is expected to occurInternal337
medication-admin-statusA set of codes indicating the current status of a MedicationAdministration.Internal330
medication-as-needed-reasonThis value set includes all clinical findings from SNOMED CT - provided as an exemplar value set.SNOMED CT89
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 CT360
medication-dispense-categoryA code describing where the dispensed medication is expected to be consumed or administeredInternal341
medication-dispense-statusA coded concept specifying the state of the dispense event.Internal339
medication-form-codesThis value set includes all dose form codes from SNOMED CT - provided as an exemplar.SNOMED CT359
medication-request-categoryA coded concept identifying the category of medication request. For example, where the medication is to be consumed or administered, or the type of medication treatment).Internal348
medication-request-intentThe kind of medication orderInternal345
medication-request-priorityIdentifies the level of importance to be assigned to actioning the requestInternal350
medication-request-statusA coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescriptionInternal343
medication-statement-categoryA coded concept identifying where the medication included in the medicationstatement is expected to be consumed or administeredInternal355
medication-statement-statusA coded concept indicating the current status of a MedicationStatement.Internal352
medication-statement-takenA coded concept identifying level of certainty if patient has taken or has not taken the medicationInternal357
medication-statusA coded concept defining if the medication is in active useInternal363
message-eventsOne of the message events defined as part of FHIR.Internal25
message-reason-encounterExample Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.Internal365
message-significance-categoryThe impact of the content of a message.Internal178
message-transportThe protocol used for message transport.Internal174
messageheader-response-requestHL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message.Internal843
metric-calibration-stateDescribes the state of a metric calibration.Internal636
metric-calibration-typeDescribes the type of a metric calibration.Internal634
metric-categoryDescribes the category of the metric.Internal632
metric-colorDescribes the typical color of representation.Internal638
metric-operational-statusDescribes the operational status of the DeviceMetric.Internal630
missing-tooth-reasonThis value set includes sample Missing Tooth Reason codes.Internal526
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 CT375
name-assembly-orderA code that represents the preferred display order of the components of a human nameInternal, V2, V3832
name-part-qualifierA set of codes each of which specifies a certain subcategory of the name part in addition to the main name part typeV3825
name-useThe use of a human nameInternal58
name-v3-representationA set of codes for each different representation of a nameV3828
namingsystem-identifier-typeIdentifies the style of unique identifier used to identify a namespace.Internal485
namingsystem-typeIdentifies the purpose of the naming system.Internal483
narrative-statusThe status of a resource narrativeInternal50
network-typeThe type of network access point of this agent in the audit eventInternal449
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
no-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 not administered. This value set is provided as a suggestive example.V3, SNOMED CT286
note-typeThe presentation types of notes.Internal15
nutrient-codeNutrientModifier : Codes for types of nutrient that is 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. It is provided as a suggestive example.SNOMED CT373
nutrition-request-statusCodes specifying the state of the request. Describes the lifecycle of the nutrition order.Internal369
object-roleCode representing the role the entity played in the audit eventInternal453
observation-categoryObservation Category codes.Internal392
observation-codesThis value set includes all LOINC codesLOINC383
observation-interpretationThis value set defines the set of codes that can be used to indicate the meaning/use of a reference range.V2386
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 CT382
observation-statisticsThe statistical operation parameter -"statistic" - codesInternal394
observation-statusCodes providing the status of an observation.Internal387
observation-valueabsentreasonThis value set defines the set of codes for identifying the reason why the expected result in Observation.value[x] is missing.Internal, V3391
observation-vitalsignresultThis value set indicates the allowed vital sign result types. The concept 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-kindWhether an operation is a normal operation or a query.Internal499
operation-outcomeOperation Outcome codes used by FHIR test servers (see Implementation file translations.xml)Internal401
operation-parameter-useWhether an operation parameter is an input or an output parameter.Internal501
operational-statusCodes representing the current status of the device - on, off, suspended, etc.Internal897
oral-prosthodontic-materialThis value set includes sample Oral Prosthodontic Material type codes.Internal530
organization-typeThis example value set defines a set of codes that can be used to indicate a type of organization.Internal403
parameter-groupCodes identifying groupings of parameters; e.g. Cardiovascular.Internal901
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.V3840
participant-roleRoles of Participants that may be included in a CarePlan.Participants, or in an EpisodeOfCare.CareTeam. Defined as: Is a Person, Healthcare professional (occupation) or Healthcare related organization (qualifier value).SNOMED CT143
participantrequiredIs the Participant required to attend the appointment.Internal481
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, Internal, DICOM920
participationstatusThe Participation status of an appointment.Internal479
payeetypeThis value set includes sample Payee Type codes.Internal30
payment-adjustment-reasonThis value set includes smattering of Payment Adjustment Reason codes.Internal592
payment-statusThis value set includes a sample set of Payment Status codes.Internal628
payment-typeThis value set includes sample Payment Type codes.Internal626
performer-roleThis examples value set defines the set of codes that can be used to indicate a role of procedure performer.SNOMED CT424
plan-definition-typeThe type of PlanDefinitionInternal780
policyholder-relationshipThis value set includes codes for the relationship between the Policyholder and the Beneficiary (insured/covered party/patient)..Internal515
postal-address-useUses of an address not included in Address.useV3827
practitioner-roleThis example value set defines a set of codes that can be used to indicate the role of a Practitioner.Internal430
practitioner-specialtyThis example value set defines a set of codes that can be used to indicate the specialty of a Practitioner.Internal432
probability-distribution-typeCodes specifying the type of probability distributionV3826
procedure-categoryProcedure Category code: A selection of relevant SNOMED CT codes.SNOMED CT421
procedure-codeProcedure Code: All SNOMED CT procedure codes.SNOMED CT418
procedure-followupProcedure follow up codes: a selection of SNOMED CT codes relevant to procedure follow up.SNOMED CT420
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 CT422
procedure-outcomeProcedure Outcome code: A selection of relevant SNOMED CT codes.SNOMED CT419
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.Internal863
procedure-reasonThis examples value set defines the set of codes that can be used to indicate a reasons for a procedure.SNOMED CT423
process-outcomeThis value set includes sample Process Outcome codes.Internal677
process-priorityThis value set includes the financial processing priority codes.Internal544
profile-codeCodes for the meaning of the defined structure.SNOMED CT, LOINC658
property-representationHow a property is represented when serialized.Internal80
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.V3, Other, Internal429
provenance-entity-roleHow an entity was used in an activity.Internal427
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 historyV3936
provenance-history-record-activityCodes for Provenance activities that are relevant when capturing event history for resources.V3903
provider-qualificationThis value set includes sample Provider Qualification codes.Internal562
provider-taxonomyNUCC Healthcare Provider Taxonomy codesOther902
publication-statusThe lifecycle status of a Value Set or Concept Map.Internal3
quality-typeType for quality reportInternal223
quantity-comparatorHow the Quantity should be understood and represented.Internal54
question-max-occursFlags an element as having unlimited repetitionsInternal846
questionnaire-answersExample list of codes for answers to questions. (Not complete or necessarily appropriate.)SNOMED CT439
questionnaire-answers-statusLifecycle status of the questionnaire response.Internal440
questionnaire-categoryExample list of potential categories for questionnaires.SNOMED CT845
questionnaire-display-categoryCodes defining the purpose of a Questionnaire item of type 'text'.Internal852
questionnaire-item-controlStarter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire.Internal848
questionnaire-questionsExample list of codes for questions and groups of questions. (Not necessarily complete or appropriate.)LOINC434
questionnaire-usage-modeIdentifies the modes of usage of a questionnaire that should enable a particular questionnaire itemInternal854
reaction-event-certaintyStatement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event.Internal859
reaction-event-severityClinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations.Internal125
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.Internal334
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 CT332
reason-medication-status-codesThis value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplarSNOMED CT0
reference-handling-policyA set of flags that defines how references are supported.Internal192
reference-version-rulesWhether a reference needs to be version specific or version independent, or whether either can be usedInternal82
referencerange-appliestoThis value set defines a set of codes that can be used to indicate the a particular target population the reference range applies to.Other, SNOMED CT396
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.Internal384
rejection-criteriaCriterion for rejection of the specimen by laboratoryInternal932
related-artifact-typeThe type of relationship to the related artifactInternal92
related-claim-relationshipThis value set includes sample Related Claim Relationship codes.Internal560
relatedperson-relationshiptypeA set of codes that can be used to indicate the relationship between a Patient and a Related Person.V2, V3442
relationshipThis value set includes the Patient to subscriber relationship codes.Internal34
remittance-outcomeThis value set includes a Claim Processing Outcome codes.Internal13
report-action-result-codesThe results of executing an action.Internal708
report-codesThis value set includes all the LOINC codes which relate to Diagnostic Observations.LOINC228
report-participant-typeThe type of participant.Internal710
report-result-codesThe reported execution result.Internal706
report-status-codesThe current status of the test report.Internal712
repository-typeType for access of external URIInternal225
request-intentCodes indicating the degree of authority/intentionality associated with a requestInternal104
request-priorityThe clinical priority of a diagnostic order.Internal106
request-statusCodes identifying the stage lifecycle stage of a requestInternal102
research-study-objective-typeCodes for the kind of study objectiveInternal0
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.Internal0
research-study-prim-purp-typeCodes for the main intent of the studyInternal0
research-study-reason-stoppedCodes for why the study ended prematurelyInternal0
research-study-statusCodes that convey the current status of the research studyInternal802
research-subject-statusIndicates the progression of a study subject through a studyInternal804
resource-aggregation-modeHow resource references can be aggregated.Internal78
resource-slicing-rulesHow slices are interpreted when evaluating an instance.Internal76
resource-statusThe master set of status codes used through out FHIR. All status codes are mapped to one of these codes.Internal0
resource-type-linkThe type of payee ResourceInternal606
resource-typesOne of the resource types defined as part of FHIR.Internal26
resource-validation-modeCodes indicating the type of validation to performInternal108
response-codeThe kind of response to a messageInternal367
restful-capability-modeThe mode of a RESTful capability statement.Internal166
restful-security-serviceTypes of security services used with FHIR.Internal168
risk-probabilityCodes representing the likelihood of a particular outcome in a risk assessment.Internal443
route-codesThis value set includes all Route codes from SNOMED CT - provided as an exemplar.SNOMED CT91
search-comparatorWhat Search Comparator Codes are supported in searchInternal622
search-entry-modeWhy an entry is in the result set - whether it's included as a match or because of an _include requirement.Internal614
search-modifier-codeA supported modifier for a search parameter.Internal624
search-param-typeData 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.Internal620
security-labelsA single value set for all security labels defined by FHIR.Other46
sequence-quality-methodThis value set includes sequence quality methodOther218
sequence-quality-standardSequenceThis value set includes sequence quality standardOther217
sequence-referenceSeqThis value set includes all Reference codesOther216
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 CT205
sequence-typeType if a sequence -- DNA, RNA, or amino acid sequenceInternal214
service-categoryThis value set defines an example set of codes that can be used to classify groupings of service-types/specialties.Internal510
service-modifiersThis value set includes sample Service Modifier codes.Internal564
service-pharmacyThis value set includes a smattering of Pharmacy Service codes.Internal554
service-placeThis value set includes a smattering of Service Place codes.Internal556
service-productThis value set includes a smattering of Service/Product codes.Internal552
service-provision-conditionsThe code(s) that detail the conditions under which the healthcare service is available/offered.Internal508
service-referral-methodThe methods of referral can be used when referring to a specific HealthCareService resource.Internal504
service-typeThis value set defines an example set of codes of service-types.Internal512
service-usclsThis value set includes a smattering of USCLS codes.Internal534
servicerequest-categoryAn example value set of SNOMED CT concepts that can classify a requested serviceSNOMED CT0
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.V3841
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.Other56
slotstatusThe free/busy status of the slot.Internal475
special-valuesA set of generally useful codes defined so they can be included in value sets.Internal9
specification-typeCodes for device specification types such as serial number, part number, hardware revision, software revision, etc.Internal899
specimen-collection-method This example value set defines a set of codes that can be used to indicate the method of collection of a specimen. It includes values from HL7 v2 table 0048.SNOMED CT, V2461
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.Other856
specimen-contained-preferenceDegree of preference of a type of conditioned specimenInternal928
specimen-container-typeThis is an example value set that includes all the LOINC codes for serum/plasma cholesterol from v2.36.LOINC463
specimen-processing-procedureThe technique that is used to perform the process or preserve the specimen.V2462
specimen-statusCodes providing the status/availability of a specimen.Internal464
structure-definition-kindDefines the type of structure that a definition is describing.Internal654
subscription-channel-typeThe type of method used to execute a subscription.Internal493
subscription-statusThe status of a subscription.Internal495
subscription-tagTags to put on a resource after subscriptions have been sent.Internal497
substance-categorySubstance category codesInternal469
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)) adn where concept is-a 373873005 (Pharmaceutical / biologic product (product))SNOMED CT466
substance-statusA code to indicate if the substance is actively usedInternal467
supplement-typeSupplementType : Codes for nutritional supplements to be provided to the patient. This value set is is composed of SNOMED CT (US Extension) Concepts from SCTID 470581016 (Enteral+supplement feeds hierarchy (product)) and is provided as a suggestive example.SNOMED CT377
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 CT685
supplydelivery-statusStatus of the supply delivery.Internal686
supplydelivery-typeThis value sets refers to a specific supply item.Internal688
supplyrequest-kindThis value sets refers to a Category of supply.Internal679
supplyrequest-reasonWhy the supply item was requestedInternal683
supplyrequest-statusStatus of the supply requestInternal681
surfaceThis value set includes a smattering of FDI tooth surface codes.Internal538
system-restful-interactionOperations supported by REST at the system level.Internal171
system-version-processing-modeHow to manage the intersection between a fixed version in a value set, and a fixed version of the system in the expansion profileInternal260
task-performer-typeThe type(s) of task performers allowedInternal771
task-statusThe current status of the task.Internal773
teethThis value set includes the FDI Teeth codes.Internal542
template-status-codeThe status indicates the level of maturity of the design and may be used to manage the use of the designOther842
testscript-operation-codesThis value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool.Internal690
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.Internal702
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.Internal700
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 CT374
timing-abbreviationCode for a known / defined timing pattern.V371
toothThis value set includes a smattering of FDI oral site codes.Internal532
transaction-modeA code that indicates how transactions are supported.Internal182
trigger-typeThe type of triggerInternal96
type-derivation-ruleHow a type relates to its baseDefinition.Internal659
type-restful-interactionOperations supported by REST at the type or instance level.Internal170
ucum-bodylengthUCUM units for recording Body Length measures such as height and head circumferenceFHIR873
ucum-bodytempUCUM units for recording Body TemperatureFHIR872
ucum-bodyweightUCUM units for recording Body WeightFHIR871
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 codesFHIR831
ucum-vitals-commonCommon UCUM units for recording Vital SignsFHIR870
udiThis value set includes sample UDI codes.Internal546
udi-entry-typeCodes to identify how UDI data was enteredInternal201
units-of-timeA unit of time (units from UCUM).FHIR70
unknown-content-codeA code that indicates whether an application accepts unknown elements or extensions when reading resources.Internal186
usage-context-typeA code that specifies a type of context being specified by a usage contextInternal94
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 CT27
usersession-statusThe status of the user sessionInternal0
usersession-status-sourceThe source of the status of the user sessionInternal0
usps-stateThis value set defines two letter USPS alphabetic codes.Other40
vaccination-protocol-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.Internal288
vaccination-protocol-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.Internal290
vaccination-protocol-dose-targetThe 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 vaccine. This value set is provided as a suggestive example and includes the SNOMED CT concepts from the 64572001 (Disease) hierarchy.SNOMED CT287
vaccine-codeThis identifies the vaccine substance administered - CVX codes.Internal, Other22
variant-stateCodes providing the status of the variant test resultInternal210
versioning-policyHow the system supports versioning for a resource.Internal180
vision-base-codesA coded concept listing the base codes.Internal646
vision-eye-codesA coded concept listing the eye codes.Internal644
vision-productThis value set includes a smattering of Prescription Product codes.Internal642
yesnodontknowFor Capturing simple yes-no-don't know answersOther, Internalnull
Name (URI = http://hl7.org/fhir/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 correctness.1.113883.1.11.155
AcknowledgementDetailCode OpenIssue: Missing description.--
AcknowledgementDetailType A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'.1.113883.1.11.19358
AcknowledgementType This attribute contains an acknowledgement code as described in the HL7 message processing rules. OpenIssue: Description was copied from attribute and needs to be improved to be appropriate for a code system..1.113883.1.11.8
ActClass**** MISSING DEFINITIONS ****.1.113883.1.11.11527
ActClassClinicalDocument A clinical document is a documentation of clinical observations and services, with the following characteristics: (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care; (3) Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document; (5) Human readability - A clinical document is human readable.".1.113883.1.11.13948
ActClassDocument Specialization of Act to add the characteristics unique to document management services..1.113883.1.11.18938
ActClassInvestigation An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government..1.113883.1.11.20224
ActClassObservation Description: An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. Thecode attribute of Observation and thevalue attribute of Observation must be considered in combination to determine the semantics of the observation. Discussion: Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter. As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects. The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology. An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations. Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC. Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation. Examples: Recording the results of a Family History Assessment Laboratory test and associated result Physical exam test and associated result Device temperature Soil lead level.1.113883.1.11.11529
ActClassProcedure An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. Examples: : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc..1.113883.1.11.19665
ActClassROI Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present..1.113883.1.11.17893
ActClassSupply Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply..1.113883.1.11.11535
ActCode A code specifying the particular kind of Act that the Act-instance represents within its class. Constraints: The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc. Conceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure. Act.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code "potassium" together with and Act.classCode for "laboratory observation" to somehow mean "potassium laboratory observation" and then use the same Act.code for "potassium" together with Act.classCode for "medication" to mean "substitution of potassium". This mutually modifying use of Act.code and Act.classCode is not permitted.--
ActConsentDirective ActConsentDirective codes are used to specify the type of Consent Directive to which a Consent Directive Act conforms..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..1.113883.1.11.19897
ActCoverageTypeCode Definition: Set of codes indicating the type of insurance policy or program that pays for the cost of benefits provided to covered parties..1.113883.1.11.19855
ActEncounterCode Domain provides codes that qualify the ActEncounterClass (ENC).1.113883.1.11.13955
ActExposureLevelCode A qualitative measure of the degree of exposure to the causative agent. This includes concepts such as "low", "medium" and "high". This quantifies how the quantity that was available to be administered to the target differs from typical or background levels of the substance.--
ActIncidentCode Set of codes indicating the type of incident or accident..1.113883.1.11.16508
ActInvoiceElementModifier Processing consideration and clarification codes..1.113883.1.11.17704
ActInvoiceGroupCode Type of invoice element that is used to assist in describing an Invoice that is either submitted for adjudication or for which is returned on adjudication results. Invoice elements of this type signify a grouping of one or more children (detail) invoice elements. They do not have intrinsic costing associated with them, but merely reflect the sum of all costing for it's immediate children invoice elements..1.113883.1.11.19398
ActMood OpenIssue: In Ballot 2009May, a strong Negative vote was lodged against several of the concept definitions in the vocabulary used for Act.moodCode. The vote was found "Persuasive With Mod", with the understanding that M and M would undertake a detailed review of these concept definitions for a future release of the RIM..1.113883.1.11.10196
ActMoodIntent An intention or plan to perform a service. Historical note: in previous RIM versions, the intent mood was captured as a separate class hierarchy, called Service_intent_or_order..1.113883.1.11.10199
ActMoodPredicate Any of the above service moods (e.g., event, intent, or goal) can be turned into a predicate used as a criterion to express conditionals (or queries.) However, currently we allow only criteria on service events..1.113883.1.11.10202
ActPharmacySupplyType Identifies types of dispensing events.1.113883.1.11.16208
ActPriority A set of codes (e.g., for routine, emergency), specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.--
ActReason A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law".--
ActRelationshipCheckpoint**** MISSING DEFINITIONS ****.1.113883.1.11.10349
ActRelationshipConditional Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred.1.113883.1.11.18977
ActRelationshipFulfills The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act..1.113883.1.11.10342
ActRelationshipHasComponent A collection of sub-services as steps or subtasks performed for the source service. Services may be performed sequentially or concurrently..1.113883.1.11.10318
ActRelationshipJoin**** MISSING DEFINITIONS ****.1.113883.1.11.10360
ActRelationshipPertains This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays..1.113883.1.11.10329
ActRelationshipSplit**** MISSING DEFINITIONS ****.1.113883.1.11.10355
ActRelationshipSubset <ns1:p>Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.</ns1:p><ns1:p>Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.</ns1:p>.1.113883.1.11.19613
ActRelationshipType The source is an excerpt from the target..1.113883.1.11.10317
ActSite An anatomical location on an organism which can be the focus of an act.--
ActStatus Codes representing the defined possible states of an Act, as defined by the Act class state machine..1.113883.1.11.15933
ActSubstanceAdminSubstitutionCodeNo Description Provided.1.113883.1.11.16621
ActTaskCode Description: A task or action that a user may perform in a clinical information system..1.113883.1.11.19846
ActUSPrivacyLaw A jurisdictional mandate in the US relating to privacy. Deprecation Comment: Content moved to ActCode under _ActPrivacyLaw; use that instead.--
ActUncertainty OpenIssue: Missing Description.1.113883.1.11.16899
AddressPartType Description: Code that specifies whether an address part names the street, city, country, postal code, post box, etc. Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line".1.113883.1.11.10642
AddressUse Codes that provide guidance around the circumstances in which a given address should be used..1.113883.1.11.190
AdministrativeGender The gender of a person used for adminstrative purposes (as opposed to clinical gender).1.113883.1.11.1
AmericanIndianAlaskaNativeLanguages American Indian and Alaska Native languages currently being used in the United States.--
Calendar**** MISSING DEFINITIONS ****.1.113883.1.11.17422
CalendarCycle Calendar cycle identifiers--
CalendarType**** MISSING DEFINITIONS ****.1.113883.1.11.10682
Charset Internet Assigned Numbers Authority (IANA) Charset Types.1.113883.1.11.14853
CodingRationale Identifies how to interpret the instance of the code, codeSystem value in a set of translations. Since HL7 (or a government body) may mandate that codes from certain code systems be sent in conformant messages, other synonyms that are sent in the translation set need to be distinguished among the originally captured source, the HL7 specified code, or some future role. When this code is NULL, it indicates that the translation is an undefined type. When valued, this property must contain one of the following values: SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination) There may be additional values added to this value set as we work through the use of codes in messages and determine other Use Cases requiring special interpretation of the translations..1.113883.1.11.19250
CommunicationFunctionType Describes the type of communication function that the associated entity plays in the associated transmission..1.113883.1.11.16031
Compartment A named tag set for metadata used to populate a security category label field that "segments" an IT resource per policy by indicating that access and use is restricted to members of a defined community or project. (HL7 Healthcare Privacy and Security Classification System) Usage Note: This is the healthcare analog to the US Intelligence Community's concept of a Special Access Program. Compartment codes may be used in as a field value in an initiator's clearance to indicate permission to access and use an IT Resource with a security label having the same compartment value in security category label field. Map: Aligns with ISO 2382-8 definition of Compartment - "A division of data into isolated blocks with separate security controls for the purpose of reducing risk.".1.113883.1.11.20478
CompressionAlgorithm**** MISSING DEFINITIONS ****.1.113883.1.11.10620
Confidentiality A set of codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality".--
ConfidentialityClassification Set of codes used to value Act.Confidentiality and Role.Confidentiality attribute in accordance with the definition for concept domain "Confidentiality"..1.113883.1.11.10228
ContainerCap The type of cap associated with a container--
ContainerSeparator A material in a blood collection container that facilites the separation of of blood cells from serum or plasma.1.113883.1.11.14054
ContentProcessingMode Description: Identifies the order in which content should be processed..1.113883.1.11.19823
ContextControl A code that specifies how an ActRelationship or Participation contributes to the context of an Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see also attributes Participation.contextControlCode, ActRelationship.contextControlCode, ActRelationship.contextConductionInd)..1.113883.1.11.16478
DataOperation**** MISSING DEFINITIONS ****--
DeviceAlertLevel Domain values for the Device.Alert_levelCode.1.113883.1.11.14066
DocumentCompletion Identifies the current completion state of a clinical document..1.113883.1.11.271
DocumentSectionType The type of document section. Possible values: review of systems, medical history, family history, microscopic findings, etc..1.113883.1.11.10871
DocumentStorage Identifies the storage status of a document.--
EducationLevel Years of education that a person has completed.1.113883.1.11.19175
EmployeeJobClass**** MISSING DEFINITIONS ****.1.113883.1.11.16036
EncounterAdmissionSource**** MISSING DEFINITIONS ****.1.113883.1.11.12234
EncounterSpecialCourtesy**** MISSING DEFINITIONS ****.1.113883.1.11.12242
EntityClass Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing..1.113883.1.11.10882
EntityClassDevice A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity. The kind of device is identified by the code attribute inherited from Entity. Usage: This includes durable (reusable) medical equipment as well as disposable equipment..1.113883.1.11.11623
EntityClassLivingSubject Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject.).1.113883.1.11.10884
EntityClassManufacturedMaterial Corresponds to the ManufacturedMaterial class.1.113883.1.11.13934
EntityClassOrganization A social or legal structure formed by human beings..1.113883.1.11.10889
EntityClassPlace A physicial place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant..1.113883.1.11.10892
EntityClassRoot Corresponds to the Entity class.1.113883.1.11.13922
EntityCode OpenIssue: Missing description.--
EntityDeterminer EntityDeterminer in natural language grammar is the class of words that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing..1.113883.1.11.10878
EntityDeterminerDetermined The described determiner is used to indicate that the given Entity is taken as a general description of a kind of thing that can be taken in whole, in part, or in multiples..1.113883.1.11.10879
EntityHandling**** MISSING DEFINITIONS ****.1.113883.1.11.13988
EntityNamePartQualifier OpenIssue: Needs description.1.113883.1.11.15888
EntityNamePartQualifierR2 Description: The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records..1.113883.1.11.20323
EntityNamePartType**** MISSING DEFINITIONS ****.1.113883.1.11.15880
EntityNamePartTypeR2 Description: Indicates whether the name part is a given name, family name, prefix, suffix, etc..1.113883.1.11.20322
EntityNameUse**** MISSING DEFINITIONS ****.1.113883.1.11.15913
EntityNameUseR2 Description: A set of codes advising a system or user which name in a set of names to select for a given purpose..1.113883.1.11.20321
EntityRisk Kinds of risks associated with the handling of the material..--
EntityStatus Codes representing the defined possible states of an Entity, as defined by the Entity class state machine..1.113883.1.11.16005
EquipmentAlertLevel**** MISSING DEFINITIONS ****.1.113883.1.11.10896
Ethnicity In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of "Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race." The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both.--
ExposureMode Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.--
FamilyMember A relationship between two people characterizing their "familial" relationship.1.113883.1.11.19579
GTSAbbreviation**** MISSING DEFINITIONS ****--
GenderStatus**** MISSING DEFINITIONS ****.1.113883.1.11.11523
GeneralPurposeOfUse Supports communication of purpose of use at a general level..1.113883.1.11.20449
HL7UpdateMode The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute..1.113883.1.11.10018
HtmlLinkType HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the current document and the anchor that is the target of the link.1.113883.1.11.11017
HumanLanguage Codes for the representation of the names of human languages..1.113883.1.11.11526
IdentifierReliability Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms..1.113883.1.11.20277
IdentifierScope Description: Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II..1.113883.1.11.20276
InformationSensitivityPolicy Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an "employee" sensitivity code would make little sense for use outside of a policy domain. "Taboo" would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.title..1.113883.1.11.20428
IntegrityCheckAlgorithm**** MISSING DEFINITIONS ****.1.113883.1.11.17385
LanguageAbilityMode A value representing the method of expression of the language. Example: Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed. OpenIssue: Description copied from Concept Domain of same name. Must be verified..1.113883.1.11.12249
LanguageAbilityProficiency A value representing the level of proficiency in a language. Example: Excellent, good, fair, poor. OpenIssue: Description copied from Concept Domain of same name. Must be verified..1.113883.1.11.12199
LivingArrangement A code depicting the living arrangements of a person--
LocalMarkupIgnore Tells a receiver to ignore just the local markup tags (local_markup, local_header, local_attr) when value="markup", or to ignore the local markup tags and all contained content when value="all".1.113883.1.11.10975
LocalRemoteControlState**** MISSING DEFINITIONS ****.1.113883.1.11.10893
ManagedParticipationStatus Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine..1.113883.1.11.15992
MapRelationship The closeness or quality of the mapping between the HL7 concept (as represented by the HL7 concept identifier) and the source coding system. The values are patterned after the similar relationships used in the UMLS Metathesaurus. Because the HL7 coding sy.1.113883.1.11.11052
MaritalStatus * * * No description supplied * * * Open Issue: The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency.--
MessageWaitingPriority Indicates that the receiver has messages for the sender OpenIssue: Description does not make sense relative to name of coding system. Must be reviewed and improved.--
MilitaryRoleType Definition: A person playing the role of program eligible under a program based on military status. Discussion: This CoveredPartyRoleType.code is typically used when the CoveredPartyRole class code is either "program eligible" or "subscriber" and the person's status as a member of the military meets jurisdictional or program criteria.1.113883.1.11.19812
ModifyIndicator**** MISSING DEFINITIONS ****.1.113883.1.11.395
NullFlavor A collection of codes specifying why a valid value is not present..1.113883.1.11.10609
ObligationPolicy Conveys the mandated workflow action that an information custodian, receiver, or user must perform. Examples: encrypt Usage Note: Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision..1.113883.1.11.20445
ObservationInterpretation One or more codes specifying a rough qualitative interpretation of the observation, such as "normal", "abnormal", "below normal", "change up", "resistant", "susceptible", etc. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Note also that this might be identical to the V2 code system of interpretation codes (formerly Abnormal Flags in older versions)..1.113883.1.11.78
ObservationMethod A code that provides additional detail about the means or technique used to ascertain the observation. Examples: Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved..1.113883.1.11.20423
ObservationType Identifies the kinds of observations that can be performed.1.113883.1.11.16226
ObservationValue This domain is the root domain to which all HL7-recognized value sets for the Observation.value attribute will be linked when Observation.value has a coded data type. OpenIssue: Description copied from Concept Domain of same name. Must be corrected..--
ParticipationFunction This code is used to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE)..1.113883.1.11.10267
ParticipationIndirectTarget Target that is not substantially present in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the act..1.113883.1.11.19032
ParticipationInformationGenerator Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness)..1.113883.1.11.10251
ParticipationInformationTranscriber An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form..1.113883.1.11.19676
ParticipationMode A set of codes specifying the modality by which the Entity playing the Role is participating in the Act. Examples: Physically present, over the telephone, written communication. Rationale: Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically. Open Issue: There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies.--
ParticipationPhysicalPerformer A person who actually and principally carries out the action. Need not be the principal responsible actor, e.g. a surgery resident operating under supervision of attending surgeon, and may be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event..1.113883.1.11.10248
ParticipationSignature A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed. Examples: A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.).1.113883.1.11.10282
ParticipationTargetDirect Target that is substantially present in the service and which is directly affected by the service action (includes consumed material, devices, etc.)..1.113883.1.11.10286
ParticipationTargetLocation The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.).1.113883.1.11.10302
ParticipationTargetSubject The principle target that the service acts on. E.g. the patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects, consumables, and devices used as tools for a service are not subjects. However, a device may be a subject of a maintenance service..1.113883.1.11.19584
ParticipationType**** MISSING DEFINITIONS ****.1.113883.1.11.10901
ParticipationVerifier A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability..1.113883.1.11.10259
PatientImportance Patient VIP code.1.113883.1.11.19265
PaymentTerms Describes payment terms for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor of an invoice..1.113883.1.11.14908
PersonDisabilityType A code identifying a person's disability.--
PersonalRelationshipRoleType Types of personal relationships between two living subjects. Example: Parent, sibling, unrelated friend, neighbor.1.113883.1.11.19563
ProbabilityDistributionType**** MISSING DEFINITIONS ****.1.113883.1.11.10747
ProcessingID Codes used to specify whether a message is part of a production, training, or debugging system..1.113883.1.11.103
ProcessingMode**** MISSING DEFINITIONS ****.1.113883.1.11.207
ProvenanceEventCurrentState Specifies the state change of a target Act, such as a document or an entry, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted"..1.113883.1.11.20547
ProvenanceEventCurrentState-AS Specifies the state change of a target Act, using ActStatus codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted"..1.113883.1.11.20545
ProvenanceEventCurrentState-DC Specifies the state change of a target Act using DocuymentCompletion codes, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted"..1.113883.1.11.20546
PurposeOfUse Supports communication of purpose of use at a general level..1.113883.1.11.20448
QueryParameterValue The domain of coded values used as parameters within QueryByParameter queries.--
QueryPriority**** MISSING DEFINITIONS ****.1.113883.1.11.91
QueryRequestLimit Definition: Defines the units associated with the magnitude of the maximum size limit of a query response that can be accepted by the requesting application.--
QueryResponse A code classifying the general nature of the response to a given query. Includes whether or not data was found, or whether an error occurred..1.113883.1.11.208
QueryStatusCode A code specifying the state of the Query..1.113883.1.11.18899
Race In the United States, federal standards for classifying data on race determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define race, and they recognize the absence of an anthropological or scientific basis for racial classification. Instead, the federal standards acknowledge that race is a social-political construct in which an individual's own identification with one more race categories is preferred to observer identification. The standards use a variety of features to define five minimum race categories. Among these features are descent from "the original peoples" of a specified region or nation. The minimum race categories are American Indian or Alaska Native, Asian, Black or African American, Native Hawaiian or Other Pacific Islander, and White. The federal standards stipulate that race data need not be limited to the five minimum categories, but any expansion must be collapsible to those categories.--
RefrainPolicy Conveys prohibited actions which an information custodian, receiver, or user is not permitted to perform unless otherwise authorized or permitted under specified circumstances. Examples: prohibit redisclosure without consent directive.1.113883.1.11.20446
RelationalOperator**** MISSING DEFINITIONS ****.1.113883.1.11.209
RelationshipConjunction**** MISSING DEFINITIONS ****.1.113883.1.11.10365
ReligiousAffiliation Assigment of spiritual faith affiliation--
ResponseLevel Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include.1.113883.1.11.14761
ResponseModality Defines the timing and grouping of the response instances. OpenIssue: Description copied from Concept Domain of same name. Must be verified..1.113883.1.11.394
ResponseMode Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities..1.113883.1.11.19650
RoleClass Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains: RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity. RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity. RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between: RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity. RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into: RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement. Personal relationship which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept. OpenIssue: Description copied from Concept Domain of same name. Must be verified..1.113883.1.11.11555
RoleClassAgent An entity (player) that acts or is authorized to act on behalf of another entity (scoper)..1.113883.1.11.14006
RoleClassAssociative A general association between two entities that is neither partitive nor ontological..1.113883.1.11.19313
RoleClassManufacturedProduct Scoped by the manufacturer.1.113883.1.11.11580
RoleClassMutualRelationship A relationship that is based on mutual behavior of the two Entities as being related. The basis of such relationship may be agreements (e.g., spouses, contract parties) or they may bede facto behavior (e.g. friends) or may be an incidental involvement with each other (e.g. parties over a dispute, siblings, children)..1.113883.1.11.19316
RoleClassPartitive An association between two Entities where the playing Entity is considered in some way "part" of the scoping Entity, e.g., as a member, component, ingredient, or content. Being "part" in the broadest sense of the word can mean anything from being an integral structural component to a mere incidental temporary association of a playing Entity with a (generally larger) scoping Entity..1.113883.1.11.10429
RoleClassPassive An association for a playing Entity that is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping Entity. The playing Entity is passive in these roles (even though it may be active in other roles), in the sense that the kinds of things done to it in this role happen without an agreement from the playing Entity..1.113883.1.11.19105
RoleClassRelationshipFormal A relationship between two entities that is formally recognized, frequently by a contract or similar agreement..1.113883.1.11.10416
RoleClassRoot Corresponds to the Role class.1.113883.1.11.13940
RoleClassServiceDeliveryLocation A role played by a place at which services may be provided..1.113883.1.11.16927
RoleClassSpecimen A role played by a material entity that is a specimen for an act. It is scoped by the source of the specimen..1.113883.1.11.11591
RoleCode A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes.--
RoleLinkStatus Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine..1.113883.1.11.20413
RoleLinkType**** MISSING DEFINITIONS ****.1.113883.1.11.11603
RoleStatus Codes representing the defined possible states of an Role, as defined by the Role class state machine..1.113883.1.11.15999
RouteOfAdministration The path the administered medication takes to get into the body or into contact with the body.--
SecurityControlObservationValue Security observation values used to indicate security control metadata. V:SecurityControl is the union of V:SecurityPolicy,V:ObligationPolicy, V:RefrainPolicy, V:PurposeOfUse, and V:GeneralPurpose of Use used to populate the SecurityControlObservationValue attribute in order to convey one or more nonhierarchical security control metadata dictating handling caveats, purpose of use, dissemination controls and other refrain policies, and obligations to which a custodian or receiver is required to comply..1.113883.1.11.20471
SecurityIntegrityObservationValueNo Description Provided.1.113883.1.11.20481
SecurityPolicy Types of security policies that further specify the ActClassPolicy value set. Examples: encrypt prohibit redisclosure without consent directive.1.113883.1.11.20444
Sequencing Specifies sequence of sort order..1.113883.1.11.390
ServiceDeliveryLocationRoleType A role of a place that further classifies the setting (e.g., accident site, road side, work site, community location) in which services are delivered..1.113883.1.11.17660
SetOperator**** MISSING DEFINITIONS ****.1.113883.1.11.17416
SeverityObservation Potential values for observations of severity..1.113883.1.11.16643
SpecimenType**** MISSING DEFINITIONS ****--
SubstanceAdminSubstitutionReasonNo Description Provided.1.113883.1.11.19377
SubstitutionCondition Identifies what sort of change is permitted or has occurred between the item that was ordered/requested and the one that was/will be provided.--
TableCellHorizontalAlign These values are defined within the XHTML 4.0 Table Model.1.113883.1.11.10981
TableCellScope These values are defined within the XHTML 4.0 Table Model.1.113883.1.11.11012
TableCellVerticalAlign These values are defined within the XHTML 4.0 Table Model.1.113883.1.11.10987
TableFrame These values are defined within the XHTML 4.0 Table Model.1.113883.1.11.10992
TableRules These values are defined within the XHTML 4.0 Table Model.1.113883.1.11.11002
TargetAwareness**** MISSING DEFINITIONS ****.1.113883.1.11.10310
TelecommunicationCapabilities Description: Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address..1.113883.1.11.20312
TimingEvent**** MISSING DEFINITIONS ****.1.113883.1.11.10706
TransmissionRelationshipTypeCode Description: A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in which way..1.113883.1.11.19833
TribalEntityUS INDIAN ENTITIES RECOGNIZED AND ELIGIBLE TO RECEIVE SERVICES FROM THE UNITED STATES BUREAU OF INDIAN AFFAIRS--
VaccineManufacturer The manufacturer of a vaccine..1.113883.1.11.227
VerificationMethodNo Description Provided.1.113883.1.11.19707
hl7Realm Description: Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models) and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms. All affiliate realm codes may automatically be used as both binding realms and namespace realms. Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms. (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.) All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm. For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types. It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes. However, tooling does not currently support namepace realm codes greater than 2 characters. Open Issue: The name of the concept property "owningAffiliate" should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code. Open Issue: In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length..1.113883.1.11.20355
hl7V3Conformance Description: Identifies allowed codes for HL7aTMs v3 conformance property.--
orderableDrugForm OpenIssue: Missing description.--
substanceAdminSubstitution Identifies what sort of change is permitted or has occurred between the therapy that was ordered and the therapy that was/will be provided.--
xBasicConfidentialityKind Description: Used to enumerate the typical confidentiality constraints placed upon a clinical document. Usage Note: x_BasicConfidentialityKind is a subset of Confidentiality codes that are used as metadata indicating the receiver responsibility to comply with normally applicable jurisdictional privacy law or disclosure authorization; that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject; or that the receiver may not disclose this information except as directed by the information custodian, who may be the information subject..1.113883.1.11.16926
URI Description OID
URI (all prefixed with http://hl7.org/fhir/v2/)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
0180Record-level Event 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 (code = CVX) (parenteral, un
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
0406Organization 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
0470- Reimbursement Type Code
0472TQ Conjunction ID
0473Formulary Status
0474Organization 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 Clincial 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