Current Build
Vocabulary Work GroupMaturity Level: 3Ballot Status: Trial Use

The following names (URIs) may be used in the system element of the Coding data type. If a URI is defined here, it SHALL be used in preference to any other identifying mechanisms. If a code system is not listed here, the correct URI may be determined by working through the following list, in order:

  • the HL7 OID Registry
  • the documentation associated with the code system
  • consulting the owner of the code system
  • asking on the HL7 vocabulary mailing list

See also the list of known identifier systems that can be used in the system element of the Identifier data type. Additional identifier systems may be registered on the HL7 FHIR registry at .

Important Notes:

  • This list of names is incomplete and subject to change. Some values may be dropped and others will likely be added in the coming months as HL7 institutes formal processes around URIs in vocabulary
  • Note that some of the URNs in this list follow the URN specification in RFC 5141 for referring to standards published by ISO, such as urn:iso:std:iso:11073:10101. Where ISO standards define codes with meanings, and there is no entry in the list above, and they are not registered in the HL7 OID registry, the default URN for the code system is that defined by the RFC 5141.
  • For several of the code systems in this list, multiple systems are given. This means that the variants identified are different code systems, not just variants of the same code system
  • Any URL in is reserved for testing and documentation purposes.

Note that the code systems are available as FHIR resources - see the Downloads Page (as part of the FHIR definitions) (excluding the External code systems.

UMLS Note: The UMLS includes many code systems that do not have an entry in the table below, or in the HL7 OID registry, or on Until these code systems are registered, implementers may use the pattern[SAB], where [SAB] is the lowercase of abbreviation of the code system as provided by UMLS. e.g. The system for "Multum MediSource Lexicon" would then be Implementers choosing to use this pattern should be aware that very often, when the code system is registered, it will use a different system.

URI Source Comment OID (for non-FHIR systems)
Externally Published code systems SNOMED CT (IHTSDO ) See Using SNOMED CT with FHIR 2.16.840.1.113883.6.96 RxNorm (US NLM ) See Using RxNorm with FHIR 2.16.840.1.113883.6.88 LOINC ( ) See Using LOINC with FHIR 2.16.840.1.113883.6.1 UCUM: ( ) Case Sensitive Codes See Using UCUM with FHIR 2.16.840.1.113883.6.8 NCI Metathesaurus See Using NCI Metathesaurus with FHIR 2.16.840.1.113883. AMA CPT codes See Using CPT with FHIR 2.16.840.1.113883.6.12 NDF-RT (National Drug File – Reference Terminology) See Using NDF-RT with FHIR 2.16.840.1.113883.6.209 Unique Ingredient Identifier (UNII) See Using UNII with FHIR 2.16.840.1.113883.4.9 NDC/NHRIC Codes See Using NDC with FHIR 2.16.840.1.113883.6.69 CVX (Vaccine Administered) See Using CVX with FHIR 2.16.840.1.113883.12.292
urn:iso:std:iso:3166 ISO Country & Regional Codes See Using ISO 3166 Codes with FHIR 1.0.3166.1.2.2 DSM-5 Diagnostic and Statistical Manual of Mental Disorders, Fifth Edition (DSM-5) 2.16.840.1.113883.6.344 NUBC code system for Patient Discharge Status National Uniform Billing Committee, manual UB-04, UB form locator 17 2.16.840.1.113883.6.301.5 RadLex (Includes play book codes) 2.16.840.1.113883.6.256
ICD-9, ICD-10 WHO ) & National Variants See Using ICD-[x] with FHIR See ICD page for details
ICPC (International Classification of Primary Care) (PH3C )
NHG Table 24 ICPC-1 (NL)

2.16.840.1.113883.6.139 ICF (International Classification of Functioning, Disability and Health) (WHO ) 2.16.840.1.113883.6.254[X](/v) Version 2 tables [X] is the 4 digit identifier for a table; e.g.
Note: only some tables may be treated in this fashion. For some tables, the meaning of the code is version dependent, and so additional information must be included in the namespace, e.g., as defined in the v2 table namespace list. Version 2 codes are case sensitive.
2.16.840.1.113883.12.[X][X] A HL7 v3 code system [X] is the code system name; e.g. HL7 v3 code systems are case sensitive. see v3 list Anatomical Therapeutic Chemical Classification System (WHO ) 2.16.840.1.113883.6.73
urn:ietf:bcp:47 IETF language (see Tags for Identifying Languages - BCP 47 ) This is used for identifying language throughout FHIR. Note that usually these codes are in a code and the system is assumed
urn:ietf:bcp:13 Mime Types (see Multipurpose Internet Mail Extensions (MIME) Part Four - BCP 13 ) This is used for identifying the mime type system throughout FHIR. Note that these codes are in a code (e.g. Attachment.contentType and in these elements the system is assumed). This system is defined for when constructing value sets of mime type codes
urn:iso:std:iso:11073:10101 Medical Device Codes defined in ISO 11073-10101 (see RTM Management service ) The ISO/IEEE 11073-10201 Terminology Code is used in the code element, and the Terminology Reference ID is used in the display element (CODE10 and REFID in the reference) 2.16.840.1.113883.6.24 DICOM Code Definitions The meanings of codes defined in DICOM, either explicitly or by reference to another part of DICOM or an external reference document or standard 1.2.840.10008.2.16.4 Health Canada Drug Identification Number

A computer-generated eight digit number assigned by Health Canada to a drug product prior to being marketed in Canada. Canada Health Drug Product Database contains product specific information on drugs approved for use in Canada.

2.16.840.1.113883.5.1105 NUCC Provider Taxonomy

The Health Care Provider Taxonomy code is a unique alphanumeric code, ten characters in length. The code set is structured into three distinct "Levels" including Provider Type, Classification, and Area of Specialization.

Code Systems for Genetics HGNC: Human Gene Nomenclature Committee 2.16.840.1.113883.6.281 ENSEMBL reference sequence identifiers Maintained jointly by the European Bioinformatics Institute and Welcome Trust Sanger Institute not assigned yet REFSEQ : National Center for Biotechnology Information (NCBI) Reference Sequences 2.16.840.1.113883.6.280 ClinVar NCBI central repository for curating pathogenicity of potentially clinically relevant variants not assigned yet Sequence Ontology not assigned yet HGVS : Human Genome Variation Society 2.16.840.1.113883.6.282 DBSNP : Single Nucleotide Polymorphism database 2.16.840.1.113883.6.284
COSMIC : Catalogue Of Somatic Mutations In Cancer 2.16.840.1.113883.3.912 LRG : Locus Reference Genomic Sequences 2.16.840.1.113883.6.283 OMIM : Online Mendelian Inheritance in Man 2.16.840.1.113883.6.174 PubMed 2.16.840.1.113883.13.191 PHARMGKB : Pharmacogenomic Knowledge Base 2.16.840.1.113883.3.913 2.16.840.1.113883.3.1077 European Bioinformatics Institute 2.16.840.1.113883.6.341
URI (all prefixed with Description OID
CodeSystem/applicability BenefitCostApplicability: Whether the cost applies to in-network or out-of-network providers. 2.16.840.1.113883.4.642.1.0
CodeSystem/can-push-updates can-push-updates: Ability of the primary source to push updates/alerts 2.16.840.1.113883.4.642.1.897
CodeSystem/example ACME Codes for Cholesterol in Serum/Plasma: This is an example code system that includes all the ACME codes for serum/plasma cholesterol from v2.36.
CodeSystem/failure-action failure-action: The result if validation fails 2.16.840.1.113883.4.642.1.891
CodeSystem/media-type MediaType: Codes for high level media categories. 2.16.840.1.113883.4.642.1.326
CodeSystem/need need: The frequency with which the target must be validated 2.16.840.1.113883.4.642.1.883
CodeSystem/primary-source-type primary-source-type: Type of the validation primary source 2.16.840.1.113883.4.642.1.893
CodeSystem/push-type-available push-type-available: Type of alerts/updates the primary source can send 2.16.840.1.113883.4.642.1.899
CodeSystem/status status: The validation status of the target 2.16.840.1.113883.4.642.1.885
CodeSystem/summary Code system summary example for ACME body sites: This is an example code system summary for the ACME codes for body site.
CodeSystem/validation-process validation-process: The primary process by which the target is validated 2.16.840.1.113883.4.642.1.889
CodeSystem/validation-status validation-status: Status of the validation of the target against the primary source 2.16.840.1.113883.4.642.1.895
CodeSystem/validation-type validation-type: What the target is validated against 2.16.840.1.113883.4.642.1.887
FDI-surface Surface Codes: This value set includes a smattering of FDI tooth surface codes. 2.16.840.1.113883.4.642.1.547
abstract-types N AbstractType: A list of the base types defined by this version of the FHIR specification - types that are defined, but for which only specializations actually are created
account-status AccountStatus: Indicates whether the account is available to be used. 2.16.840.1.113883.4.642.1.727
action-cardinality-behavior ActionCardinalityBehavior: Defines behavior for an action or a group for how many times that item may be repeated 2.16.840.1.113883.4.642.1.808
action-condition-kind ActionConditionKind: Defines the kinds of conditions that can appear on actions 2.16.840.1.113883.4.642.1.816
action-grouping-behavior ActionGroupingBehavior: Defines organization behavior of a group 2.16.840.1.113883.4.642.1.800
action-participant-type ActionParticipantType: The type of participant for the action 2.16.840.1.113883.4.642.1.812
action-precheck-behavior ActionPrecheckBehavior: Defines selection frequency behavior for an action or group 2.16.840.1.113883.4.642.1.806
action-relationship-type ActionRelationshipType: Defines the types of relationships between actions 2.16.840.1.113883.4.642.1.814
action-required-behavior ActionRequiredBehavior: Defines requiredness behavior for selecting an action or an action group 2.16.840.1.113883.4.642.1.804
action-selection-behavior ActionSelectionBehavior: Defines selection behavior of a group 2.16.840.1.113883.4.642.1.802
action-type ActionType: The type of action to be performed 2.16.840.1.113883.4.642.1.810
actionlist ActionList: List of allowable action which this resource can request. 2.16.840.1.113883.4.642.1.690
activity-definition-category ActivityDefinitionCategory: High-level categorization of the type of activity 2.16.840.1.113883.4.642.1.793
additionalmaterials Additional Material Codes: This value set includes sample additional material type codes. 2.16.840.1.113883.4.642.1.530
address-type AddressType: The type of an address (physical / postal) 2.16.840.1.113883.4.642.1.70
address-use AddressUse: The use of an address 2.16.840.1.113883.4.642.1.68
adjudication Adjudication Value Codes: This value set includes a smattering of Adjudication Value codes which includes codes to indicate the amounts eligible under the plan, the amount of benefit, copays etc. 2.16.840.1.113883.4.642.1.597
adjudication-error Adjudication Error Codes: This value set includes a smattering of adjudication codes. 2.16.840.1.113883.4.642.1.40
adjudication-reason Adjudication Reason Codes: This value set includes smattering of Adjudication Reason codes. 2.16.840.1.113883.4.642.1.599
administrative-gender N AdministrativeGender: The gender of a person used for administrative purposes. 2.16.840.1.113883.4.642.1.2
admit-source AdmitSource: This value set defines a set of codes that can be used to indicate from where the patient came in. 2.16.840.1.113883.4.642.1.258
adverse-event-actuality AdverseEventActuality: Overall nature of the event, e.g. real or potential 2.16.840.1.113883.4.642.1.832
adverse-event-category AdverseEventCategory: Overall categorization of the event, e.g. product related or situational 2.16.840.1.113883.4.642.1.834
adverse-event-causality-assess AdverseEventCausalityAssessment: TODO 2.16.840.1.113883.4.642.1.841
adverse-event-causality-method AdverseEventCausalityMethod: TODO 2.16.840.1.113883.4.642.1.843
adverse-event-outcome AdverseEventOutcome: TODO (and should this be required?) 2.16.840.1.113883.4.642.1.837
adverse-event-seriousness AdverseEventSeriousness: Overall seriousness of this event for the patient 2.16.840.1.113883.4.642.1.839
adverse-event-severity AdverseEventSeverity: The severity of the adverse event itself, in direct relation to the subject 2.16.840.1.113883.4.642.1.845
allerg-intol-substance-exp-risk AllergyIntoleranceSubstanceExposureRisk: The risk of an adverse reaction (allergy or intolerance) for this patient upon exposure to the substance (including pharmaceutical products). 2.16.840.1.113883.4.642.1.941
allergy-clinical-status AllergyIntoleranceClinicalStatus: The clinical status of the allergy or intolerance. 2.16.840.1.113883.4.642.1.128
allergy-intolerance-category AllergyIntoleranceCategory: Category of an identified substance. 2.16.840.1.113883.4.642.1.134
allergy-intolerance-criticality AllergyIntoleranceCriticality: Estimate of the potential clinical harm, or seriousness, of a reaction to an identified substance. 2.16.840.1.113883.4.642.1.130
allergy-intolerance-type AllergyIntoleranceType: Identification of the underlying physiological mechanism for a Reaction Risk. 2.16.840.1.113883.4.642.1.132
allergy-verification-status AllergyIntoleranceVerificationStatus: Assertion about certainty associated with a propensity, or potential risk, of a reaction to the identified substance. 2.16.840.1.113883.4.642.1.126
animal-genderstatus GenderStatus: This example value set defines a set of codes that can be used to indicate the current state of the animal's reproductive organs. 2.16.840.1.113883.4.642.1.419
animal-species AnimalSpecies: This example value set defines a set of codes that can be used to indicate species of animal patients. 2.16.840.1.113883.4.642.1.421
appointmentstatus AppointmentStatus: The free/busy status of an appointment. 2.16.840.1.113883.4.642.1.485
assert-direction-codes AssertionDirectionType: The type of direction to use for assertion. 2.16.840.1.113883.4.642.1.707
assert-operator-codes AssertionOperatorType: The type of operator to use for assertion. 2.16.840.1.113883.4.642.1.709
assert-response-code-types AssertionResponseTypes: The type of response code to use for assertion. 2.16.840.1.113883.4.642.1.711
audit-entity-type AuditEventEntityType: Code for the entity type involved in the audit event. 2.16.840.1.113883.4.642.1.459
audit-event-action AuditEventAction: Indicator for type of action performed during the event that generated the event 2.16.840.1.113883.4.642.1.453
audit-event-outcome AuditEventOutcome: Indicates whether the event succeeded or failed 2.16.840.1.113883.4.642.1.455
audit-event-type Audit Event ID: Event Types for Audit Events - defined by DICOM with some FHIR specific additions. 2.16.840.1.113883.4.642.1.463
basic-resource-type Basic Resource Types: This value set defines codes for resources not yet supported by (or which will never be supported by) FHIR. Many of the codes listed here will eventually be turned into official resources. However, there is no guarantee that any particular resource will be created nor that the scope will be exactly as defined by the codes presented here. Codes in this set will be deprecated if/when formal resources are defined that encompass these concepts. 2.16.840.1.113883.4.642.1.139
benefit-network Network Type Codes: This value set includes a smattering of Network type codes. 2.16.840.1.113883.4.642.1.609
benefit-term Benefit Term Codes: This value set includes a smattering of Benefit Term codes. 2.16.840.1.113883.4.642.1.613
benefit-type Benefit Type Codes: This value set includes a smattering of Benefit type codes. 2.16.840.1.113883.4.642.1.607
benefit-unit Unit Type Codes: This value set includes a smattering of Unit type codes. 2.16.840.1.113883.4.642.1.611
binding-strength N BindingStrength: Indication of the degree of conformance expectations associated with a binding. 2.16.840.1.113883.4.642.1.44
bundle-type N BundleType: Indicates the purpose of a bundle - how it was intended to be used. 2.16.840.1.113883.4.642.1.621
capability-statement-kind N CapabilityStatementKind: How a capability statement is intended to be used. 2.16.840.1.113883.4.642.1.199
care-plan-activity-status CarePlanActivityStatus: Indicates where the activity is at in its overall life cycle. 2.16.840.1.113883.4.642.1.147
care-team-category CareTeamCategory: Indicates the type of care team. 2.16.840.1.113883.4.642.1.156
care-team-status CareTeamStatus: Indicates the status of the care team. 2.16.840.1.113883.4.642.1.154
catalogType CatalogType: The type of catalog 2.16.840.1.113883.4.642.1.969
chargeitem-billingcodes ChargeItemCode: Example set of codes that can be used for billing purposes 2.16.840.1.113883.4.642.1.849
chargeitem-status ChargeItemStatus: Codes identifying the lifecycle stage of a ChargeItem 2.16.840.1.113883.4.642.1.847
choice-list-orientation ChoiceListOrientation: Direction in which lists of possible answers should be displayed 2.16.840.1.113883.4.642.1.934
chromosome-human chromosome-human: Chromosome number for human 2.16.840.1.113883.4.642.1.225
claim-exception Exception Codes: This value set includes sample Exception codes. 2.16.840.1.113883.4.642.1.581
claim-type Claim Type Codes: This value set includes Claim Type codes. 2.16.840.1.113883.4.642.1.1011
claim-use Use: Complete, proposed, exploratory, other 2.16.840.1.113883.4.642.1.545
claimcareteamrole Claim Care Team Role Codes: This value set includes sample Claim Care Team Role codes. 2.16.840.1.113883.4.642.1.587
claiminformationcategory Claim Information Category Codes: This value set includes sample Information Category codes. 2.16.840.1.113883.4.642.1.583
code-search-support CodeSearchSupport: The degree to which the server supports the code search parameter on ValueSet, if it is supported 2.16.840.1.113883.4.642.1.861
codesystem-altcode-kind AlternativeCodeKind: Indicates the type of use for which the code is defined 2.16.840.1.113883.4.642.1.953
codesystem-content-mode N CodeSystemContentMode: How much of the content of the code system - the concepts and codes it defines - are represented in a code system resource 2.16.840.1.113883.4.642.1.783
codesystem-hierarchy-meaning N CodeSystemHierarchyMeaning: The meaning of the hierarchy of concepts in a code system 2.16.840.1.113883.4.642.1.785
common-tags Common Tags: Common Tag Codes defined by FHIR project 2.16.840.1.113883.4.642.1.80
communication-category CommunicationCategory: Codes for general categories of communications such as alerts, instruction, etc. 2.16.840.1.113883.4.642.1.173
communication-not-done-reason CommunicationNotDoneReason: Codes for the reason why a communication was not done. 2.16.840.1.113883.4.642.1.175
communication-topic CommunicationTopic: Codes describing the purpose or content of the communication. 2.16.840.1.113883.4.642.1.984
compartment-type CompartmentType: Which compartment a compartment definition describes 2.16.840.1.113883.4.642.1.787
composite-measure-scoring CompositeMeasureScoring: The composite scoring method of the measure 2.16.840.1.113883.4.642.1.774
composition-attestation-mode CompositionAttestationMode: The way in which a person authenticated a composition. 2.16.840.1.113883.4.642.1.239
composition-status CompositionStatus: The workflow/clinical status of the composition. 2.16.840.1.113883.4.642.1.242
concept-map-equivalence N ConceptMapEquivalence: The degree of equivalence between concepts. 2.16.840.1.113883.4.642.1.18
concept-properties FHIR Defined Concept Properties: A set of common concept properties for use on coded systems throughout the FHIR eco-system.
concept-property-type N PropertyType: The type of a property value 2.16.840.1.113883.4.642.1.781
conceptmap-unmapped-mode N ConceptMapGroupUnmappedMode: Defines which action to take if there is no match in the group. 2.16.840.1.113883.4.642.1.481
condition-category Condition Category Codes: Preferred value set for Condition Categories. 2.16.840.1.113883.4.642.1.163
condition-clinical Condition Clinical Status Codes: Preferred value set for Condition Clinical Status. 2.16.840.1.113883.4.642.1.165
condition-state ConditionState: Enumeration indicating whether the condition is currently active, inactive, or has been resolved. 2.16.840.1.113883.4.642.1.964
condition-ver-status ConditionVerificationStatus: The verification status to support or decline the clinical status of the condition or diagnosis. 2.16.840.1.113883.4.642.1.167
conditional-delete-status N ConditionalDeleteStatus: A code that indicates how the server supports conditional delete. 2.16.840.1.113883.4.642.1.195
conditional-read-status N ConditionalReadStatus: A code that indicates how the server supports conditional read. 2.16.840.1.113883.4.642.1.201
conformance-expectation ConformanceExpectation: Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification. 2.16.840.1.113883.4.642.1.920
consent-data-meaning ConsentDataMeaning: How a resource reference is interpreted when testing consent restrictions 2.16.840.1.113883.4.642.1.760
consent-provision-type ConsentProvisionType: How a rule statement is applied, such as adding additional consent or removing consent 2.16.840.1.113883.4.642.1.758
consentaction Consent Action Codes: This value set includes sample Consent Action codes. 2.16.840.1.113883.4.642.1.754
consentcategorycodes Consent Category Codes: This value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes; HL7 VALUE SET: ActConsentType(2.16.840.1.113883.1.11.19897); examples of US realm consent directive legal descriptions and references to online and/or downloadable forms such as the SSA-827 Authorization to Disclose Information to the Social Security Administration; and other anticipated consent directives related to participation in a clinical trial, medical procedures, reproductive procedures; health care directive (Living Will); advance directive, do not resuscitate (DNR); Physician Orders for Life-Sustaining Treatment (POLST) 2.16.840.1.113883.4.642.1.752
consentperformer Performer Role Codes: This value set includes sample Performer Role codes. 2.16.840.1.113883.4.642.1.1017
consentpolicycodes Consent PolicyRule Codes: This value set includes sample Regulatory consent policy types from the US and other regions. 2.16.840.1.113883.4.642.1.1015
consentscope Consent Scope Codes: This value set includes the four Consent scope codes. 2.16.840.1.113883.4.642.1.762
constraint-severity ConstraintSeverity: SHALL applications comply with this constraint? 2.16.840.1.113883.4.642.1.82
contact-point-system ContactPointSystem: Telecommunications form for contact point 2.16.840.1.113883.4.642.1.72
contact-point-use ContactPointUse: Use of contact point 2.16.840.1.113883.4.642.1.74
contactentity-type ContactEntityType: This example value set defines a set of codes that can be used to indicate the purpose for which you would contact a contact party. 2.16.840.1.113883.4.642.1.417
container-cap ContainerCap: Color of the container cap 2.16.840.1.113883.4.642.1.851
contract-content-derivative Contract Content Derivation Codes: This is an example set of Content Derivative type codes, which represent the minimal content derived from the basal information source at a specific stage in its lifecycle, which is sufficient to manage that source information, for example, in a repository, registry, processes and workflows, for making access control decisions, and providing query responses. 2.16.840.1.113883.4.642.1.746
contract-data-meaning ContractDataMeaning: How a resource reference is interpreted when evaluating contract offers 2.16.840.1.113883.4.642.1.750
contract-status Contract Resource Status Codes: This value set contract specific codes for status. 2.16.840.1.113883.4.642.1.744
contractsubtypecodes Contract Subtype Codes: This value set includes sample Contract Subtype codes. 2.16.840.1.113883.4.642.1.732
contracttermsubtypecodes Contract Term Subtype Codes: This value set includes sample Contract Term SubType codes. 2.16.840.1.113883.4.642.1.736
contracttermtypecodes Contract Term Type Codes: This value set includes sample Contract Term Type codes. 2.16.840.1.113883.4.642.1.734
contracttypecodes Contract Type Codes: This value set includes sample Contract Type codes. 2.16.840.1.113883.4.642.1.730
contributor-type ContributorType: The type of contributor 2.16.840.1.113883.4.642.1.94
copy-number-event CopyNumberEvent: Copy Number Event 2.16.840.1.113883.4.642.1.227
coverage-class Coverage Class Codes: This value set includes Coverage Class codes. 2.16.840.1.113883.4.642.1.1010
coverage-copay-type Coverage Copay Type Codes: This value set includes sample Coverage Copayment Type codes. 2.16.840.1.113883.4.642.1.528
coverage-selfpay Coverage SelfPay Codes: This value set includes Coverage SelfPay codes. 2.16.840.1.113883.4.642.1.526
data-absent-reason N DataAbsentReason: Used to specify why the normally expected content of the data element is missing. 2.16.840.1.113883.4.642.1.6
data-types N DataType: A version specific list of the data types defined by the FHIR specification for use as an element type (any of the FHIR defined data types)
days-of-week DaysOfWeek: The days of the week. 2.16.840.1.113883.4.642.1.513
definition-status DefinitionStatus: Codes identifying the lifecycle stage of a definition 2.16.840.1.113883.4.642.1.108
definition-topic DefinitionTopic: High-level categorization of the definition, used for searching, sorting, and filtering 2.16.840.1.113883.4.642.1.795
definition-use N DefinitionUseCodes: Structure Definition Use Codes / Keywords 2.16.840.1.113883.4.642.1.0
detectedissue-severity DetectedIssueSeverity: Indicates the potential degree of impact of the identified issue on the patient. 2.16.840.1.113883.4.642.1.207
device-action Procedure Device Action Codes: Example codes indicating the change that happened to the device during the procedure. Note that these are in no way complete and might not even be appropriate for some uses. 2.16.840.1.113883.4.642.1.426
device-statement-status DeviceUseStatementStatus: A coded concept indicating the current status of a the Device Usage 2.16.840.1.113883.4.642.1.215
device-status FHIRDeviceStatus: The availability status of the device. 2.16.840.1.113883.4.642.1.210
diagnosis-role DiagnosisRole: This value set defines a set of codes that can be used to express the role of a diagnosis on the Encounter or EpisodeOfCare record. 2.16.840.1.113883.4.642.1.50
diagnostic-report-status DiagnosticReportStatus: The status of the diagnostic report. 2.16.840.1.113883.4.642.1.236
dicom-audit-lifecycle DICOM Audit Message Record Lifecycle Events: Attached is vocabulary for the record lifecycle events, as per DICOM Audit Message,
diet Diet: This value set defines a set of codes that can be used to indicate dietary preferences or restrictions a patient may have. 2.16.840.1.113883.4.642.1.256
discharge-disposition DischargeDisposition: This value set defines a set of codes that can be used to where the patient left the hospital. 2.16.840.1.113883.4.642.1.260
discriminator-type DiscriminatorType: How an element value is interpreted when discrimination is evaluated 2.16.840.1.113883.4.642.1.92
document-mode N DocumentMode: Whether the application produces or consumes documents. 2.16.840.1.113883.4.642.1.187
document-reference-status DocumentReferenceStatus: The status of the document reference. 2.16.840.1.113883.4.642.1.8
document-relationship-type DocumentRelationshipType: The type of relationship between documents. 2.16.840.1.113883.4.642.1.245
dose-rate-type DoseAndRateType: The kind of dose or rate specified 2.16.840.1.113883.4.642.1.982
eligibilityrequest-use EligibilityRequestUse: A code specifying the types of information being requested. 2.16.840.1.113883.4.642.1.0
eligibilityresponse-use EligibilityResponseUse: A code specifying the types of information being requested. 2.16.840.1.113883.4.642.1.0
encounter-location-status EncounterLocationStatus: The status of the location. 2.16.840.1.113883.4.642.1.263
encounter-special-arrangements SpecialArrangements: This value set defines a set of codes that can be used to indicate the kinds of special arrangements in place for a patients visit. 2.16.840.1.113883.4.642.1.254
encounter-status EncounterStatus: Current state of the encounter 2.16.840.1.113883.4.642.1.247
encounter-type EncounterType: This example value set defines a set of codes that can be used to indicate the type of encounter: a specific code indicating type of service provided. 2.16.840.1.113883.4.642.1.249
endpoint-connection-type Endpoint Connection Type: This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values. 2.16.840.1.113883.4.642.1.499
endpoint-payload-type Endpoint Payload Type: This is an example value set defined by the FHIR project, that could be used to represent possible payload document types. 2.16.840.1.113883.4.642.1.497
endpoint-status EndpointStatus: The status of the endpoint 2.16.840.1.113883.4.642.1.495
entformula-additive Enteral Formula Additive Type Code: EnteralFormulaAdditiveType: Codes for the type of modular component such as protein, carbohydrate or fiber to be provided in addition to or mixed with the base formula. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.393
episode-of-care-status EpisodeOfCareStatus: The status of the episode of care. 2.16.840.1.113883.4.642.1.665
episodeofcare-type EpisodeOfCareType: This example value set defines a set of codes that can be used to express the usage type of an EpisodeOfCare record. 2.16.840.1.113883.4.642.1.667
event-capability-mode N EventCapabilityMode: The mode of a message capability statement. 2.16.840.1.113883.4.642.1.183
event-status EventStatus: Codes identifying the lifecycle stage of a event 2.16.840.1.113883.4.642.1.110
event-timing EventTiming: Real world event relating to the schedule. 2.16.840.1.113883.4.642.1.76
evidence-quality QualityOfEvidenceRating: A rating system that describes the quality of evidence such as the GRADE, DynaMed, or Oxford CEBM systems 2.16.840.1.113883.4.642.1.975
ex-USCLS USCLS Codes: This value set includes a smattering of USCLS codes. 2.16.840.1.113883.4.642.1.543
ex-benefitcategory Benefit Category Codes: This value set includes a examples of Benefit Category codes. 2.16.840.1.113883.4.642.1.0
ex-claimitemtype Claim Item Type Codes: This value set includes sample Item Type codes. 2.16.840.1.113883.4.642.1.549
ex-claimsubtype Example Claim SubType Codes: This value set includes sample Claim SubType codes which are used to distinguish the claim types for example within type institutional there may be subtypes for emergency services, bedstay and transportation. 2.16.840.1.113883.4.642.1.567
ex-diagnosisrelatedgroup Example Diagnosis Related Group Codes: This value set includes example Diagnosis Related Group codes. 2.16.840.1.113883.4.642.1.589
ex-diagnosistype Example Diagnosis Type Codes: This value set includes example Diagnosis Type codes. 2.16.840.1.113883.4.642.1.591
ex-fdi Teeth Codes: This value set includes the FDI Teeth codes. 2.16.840.1.113883.4.642.1.551
ex-onsettype Example Onset Type (Reason) Codes: This value set includes example Onset Type codes which are used to identify the event for which the onset, starting date, is required. 2.16.840.1.113883.4.642.1.579
ex-oralprostho Oral Prostho Material type Codes: This value set includes sample Oral Prosthodontic Material type codes. 2.16.840.1.113883.4.642.1.539
ex-payee-resource-type ClaimPayeeResourceType: The type of Claim payee Resource 2.16.840.1.113883.4.642.1.585
ex-paymenttype Example Payment Type Codes: This value set includes example Payment Type codes. 2.16.840.1.113883.4.642.1.617
ex-pharmaservice Example Pharmacy Service Codes: This value set includes a smattering of Pharmacy Service codes. 2.16.840.1.113883.4.642.1.563
ex-programcode Example Program Reason Codes: This value set includes sample Program Reason Span codes. 2.16.840.1.113883.4.642.1.577
ex-providerqualification Example Provider Qualification Codes: This value set includes sample Provider Qualification codes. 2.16.840.1.113883.4.642.1.571
ex-relatedclaimrelationship Example Related Claim Relationship Codes: This value set includes sample Related Claim Relationship codes. 2.16.840.1.113883.4.642.1.569
ex-revenue-center Example Revenue Center Codes: This value set includes sample Revenue Center codes. 2.16.840.1.113883.4.642.1.595
ex-servicemodifier Example Service Modifier Codes: This value set includes sample Service Modifier codes which may support differential payment. 2.16.840.1.113883.4.642.1.573
ex-serviceplace Example Service Place Codes: This value set includes a smattering of Service Place codes. 2.16.840.1.113883.4.642.1.565
ex-serviceproduct Example Service/Product Codes: This value set includes a smattering of Service/Product codes. 2.16.840.1.113883.4.642.1.561
ex-tooth Oral Site Codes: This value set includes a smattering of FDI oral site codes. 2.16.840.1.113883.4.642.1.541
ex-udi UDI Codes: This value set includes sample UDI codes. 2.16.840.1.113883.4.642.1.555
ex-visionprescriptionproduct Example Vision Prescription Product Codes: This value set includes a smattering of Prescription Product codes. 2.16.840.1.113883.4.642.1.659
examplescenario-actor-type ExampleScenarioActorType: The type of actor - system or human 2.16.840.1.113883.4.642.1.859
explanationofbenefit-status ExplanationOfBenefitStatus: A code specifying the state of the resource instance. 2.16.840.1.113883.4.642.1.619
expression-language ExpressionLanguage: The media type of the expression language 2.16.840.1.113883.4.642.1.106
extension-context-type N ExtensionContextType: How an extension context is interpreted. 2.16.840.1.113883.4.642.1.1013
extra-activity-type ExtraActivityType: This value set includes coded concepts not well covered in any of the included valuesets.
extra-security-role-type SecurityRoleType: This CodeSystem contains Additional FHIR-defined Security Role types not defined elsewhere
feeding-device Feeding Device Codes: Materials used or needed to feed the patient. 2.16.840.1.113883.4.642.1.962
fhir-versions N All Published FHIR versions: A 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 labeled extensible because the list of published 2.16.840.1.113883.4.642.1.53
filter-operator N FilterOperator: The kind of operation to perform as a part of a property based filter. 2.16.840.1.113883.4.642.1.479
flag-category Flag Category: Example list of general categories for flagged issues. (Not complete or necessarily appropriate.) 2.16.840.1.113883.4.642.1.123
flag-priority-code Flag Priority Codes: This value set is provided as an exemplar. The value set is driven by IHE Table B.8-4: Abnormal Flags, Alert Priority. 2.16.840.1.113883.4.642.1.951
flag-status FlagStatus: Indicates whether this flag is active and needs to be displayed to a user, or whether it is no longer needed or entered in error. 2.16.840.1.113883.4.642.1.121
fm-conditions FM Condition Codes: This value set includes sample Conditions codes. 2.16.840.1.113883.4.642.1.557
fm-status Financial Resource Status Codes: This value set includes Status codes. 2.16.840.1.113883.4.642.1.593
forms-codes Form Codes: This value set includes a sample set of Forms codes. 2.16.840.1.113883.4.642.1.38
fundsreserve Funds Reservation Codes: This value set includes sample funds reservation type codes. 2.16.840.1.113883.4.642.1.34
gender-identity GenderIdentity: This example value set defines a set of codes that can be used to indicate a patient's gender identity. 2.16.840.1.113883.4.642.1.973
goal-acceptance-status GoalAcceptanceStatus: Codes indicating whether the goal has been accepted by a stakeholder 2.16.840.1.113883.4.642.1.918
goal-category GoalCategory: Example codes for grouping goals for filtering or presentation. 2.16.840.1.113883.4.642.1.276
goal-priority GoalPriority: Indicates the level of importance associated with reaching or sustaining a goal. 2.16.840.1.113883.4.642.1.274
goal-relationship-type GoalRelationshipType: Types of relationships between two goals 2.16.840.1.113883.4.642.1.916
goal-status GoalStatus: Indicates whether the goal has been met and is still being targeted 2.16.840.1.113883.4.642.1.272
goal-status-reason GoalStatusReason: Example codes indicating the reason for a current status. Note that these are in no way complete and might not even be appropriate for some uses. 2.16.840.1.113883.4.642.1.278
graph-compartment-rule GraphCompartmentRule: How a compartment must be linked 2.16.840.1.113883.4.642.1.281
graph-compartment-use GraphCompartmentUse: Defines how a compartment rule is used 2.16.840.1.113883.4.642.1.283
group-type GroupType: Types of resources that are part of group 2.16.840.1.113883.4.642.1.285
guidance-response-status GuidanceResponseStatus: The status of a guidance response 2.16.840.1.113883.4.642.1.818
guide-page-generation GuidePageGeneration: A code that indicates how the page is generated 2.16.840.1.113883.4.642.1.999
guide-parameter-code GuideParameterCode: Code of parameter that is input to the guide 2.16.840.1.113883.4.642.1.997
handling-condition HandlingConditionSet: Set of handling instructions prior testing of the specimen 2.16.840.1.113883.4.642.1.855
history-absent-reason FamilyHistoryAbsentReason: Codes describing the reason why a family member's history is not available. 2.16.840.1.113883.4.642.1.270
history-status FamilyHistoryStatus: A code that identifies the status of the family history record. 2.16.840.1.113883.4.642.1.268
hl7-work-group HL7Workgroup: An HL7 administrative unit that owns artifacts in the FHIR specification 2.16.840.1.113883.4.642.1.945
http-operations TestScriptRequestMethodCode: The allowable request method or HTTP operation codes. 2.16.840.1.113883.4.642.1.717
http-verb N HTTPVerb: HTTP verbs (in the HTTP command line). 2.16.840.1.113883.4.642.1.625
identifier-type Identifier Type Codes: A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. 2.16.840.1.113883.4.642.1.46
identifier-use IdentifierUse: Identifies the purpose for this identifier, if known . 2.16.840.1.113883.4.642.1.58
identity-assuranceLevel IdentityAssuranceLevel: The level of confidence that this link represents the same actual person, based on NIST Authentication Levels. 2.16.840.1.113883.4.642.1.657
imagingstudy-status ImagingStudyStatus: The status of the ImagingStudy 2.16.840.1.113883.4.642.1.991
immunization-evaluation-dose-status Immunization Evaluation Dose Status codes: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the validity of a dose relative to a particular recommended schedule. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.302
immunization-evaluation-dose-status-reason Immunization Evaluation Dose Status Reason codes: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why an administered dose has been assigned a particular status. Often, this reason describes why a dose is considered invalid. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.304
immunization-funding-source Immunization Funding Source: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the vaccine administered. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.294
immunization-origin Immunization Origin Codes: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the source of the data when the report of the immunization event is not based on information from the person, entity or organization who administered the vaccine. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.297
immunization-program-eligibility Immunization Program Eligibility: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the patient's elibigility for a vaccination program. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.292
immunization-recommendation-status Immunization Recommendation Status Codes: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the status of the patient towards perceived immunity against a vaccine preventable disease. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.306
immunization-subpotent-reason Immunization Subpotent Reason: The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the reason why a dose is considered to be subpotent. This value set is provided as a suggestive example. 2.16.840.1.113883.4.642.1.994
implant-status Implant Status: A set codes that define the functional status of an implanted device. 2.16.840.1.113883.4.642.1.949
intervention Intervention Codes: This value set includes sample Intervention codes. 2.16.840.1.113883.4.642.1.533
invoice-priceComponentType InvoicePriceComponentType: Codes indicating the kind of the price component 2.16.840.1.113883.4.642.1.869
invoice-status InvoiceStatus: Codes identifying the lifecycle stage of an Invoice 2.16.840.1.113883.4.642.1.867
iso-21089-lifecycle ISO 21089-2017 Health Record Lifecycle Events: Attached is vocabulary for the 27 record lifecycle events, as per ISO TS 21089-2017, Health Informatics - Trusted End-to-End Information Flows, Section 3, Terms and Definitions (2017, at ISO Central Secretariat, passed ballot and ready for publication). This will also be included in the FHIR EHR Record Lifecycle Event Implementation Guide, balloted and (to be) published with FHIR STU-3.
issue-severity N IssueSeverity: How the issue affects the success of the action. 2.16.840.1.113883.4.642.1.409
issue-type N IssueType: A code that describes the type of issue. 2.16.840.1.113883.4.642.1.411
item-type QuestionnaireItemType: Distinguishes groups from questions and display text and indicates data type for questions 2.16.840.1.113883.4.642.1.445
language-preference-type LanguagePreferenceType: This value set defines the set of codes for describing the type or mode of the patient's preferred language. 2.16.840.1.113883.4.642.1.1023
library-type LibraryType: The type of knowledge asset this library contains 2.16.840.1.113883.4.642.1.764
link-type N LinkType: The type of link between this patient resource and another patient resource. 2.16.840.1.113883.4.642.1.424
linkage-type LinkageType: Used to distinguish different roles a resource can play within a set of linked resources 2.16.840.1.113883.4.642.1.315
list-empty-reason List Empty Reasons: General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list). 2.16.840.1.113883.4.642.1.323
list-example-use-codes Example Use Codes for List: Example use codes for the List resource - typical kinds of use. 2.16.840.1.113883.4.642.1.317
list-mode ListMode: The processing mode that applies to this list 2.16.840.1.113883.4.642.1.319
list-order List Order Codes: Base values for the order of the items in a list resource. 2.16.840.1.113883.4.642.1.325
list-status ListStatus: The current state of the list 2.16.840.1.113883.4.642.1.327
location-mode LocationMode: Indicates whether a resource instance represents a specific location or a class of locations. 2.16.840.1.113883.4.642.1.331
location-physical-type LocationType: This example value set defines a set of codes that can be used to indicate the physical form of the Location. 2.16.840.1.113883.4.642.1.329
location-status LocationStatus: Indicates whether the location is still in use. 2.16.840.1.113883.4.642.1.333
map-context-type StructureMapContextType: How to interpret the context 2.16.840.1.113883.4.642.1.680
map-group-type-mode StructureMapGroupTypeMode: If this is the default rule set to apply for the source type, or this combination of types 2.16.840.1.113883.4.642.1.688
map-input-mode StructureMapInputMode: Mode for this instance of data 2.16.840.1.113883.4.642.1.678
map-model-mode StructureMapModelMode: How the referenced structure is used in this mapping 2.16.840.1.113883.4.642.1.676
map-source-list-mode StructureMapSourceListMode: If field is a list, how to manage the source 2.16.840.1.113883.4.642.1.684
map-target-list-mode StructureMapTargetListMode: If field is a list, how to manage the production 2.16.840.1.113883.4.642.1.686
map-transform StructureMapTransform: How data is copied/created 2.16.840.1.113883.4.642.1.682
marital-status N Marital Status Codes: This value set defines the set of codes that can be used to indicate the marital status of a person. 2.16.840.1.113883.4.642.1.30
match-grade MatchGrade: A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. 2.16.840.1.113883.4.642.1.971
measure-data-usage MeasureDataUsage: The intended usage for supplemental data elements in the measure 2.16.840.1.113883.4.642.1.772
measure-population MeasurePopulationType: The type of population 2.16.840.1.113883.4.642.1.766
measure-report-status MeasureReportStatus: The status of the measure report 2.16.840.1.113883.4.642.1.777
measure-report-type MeasureReportType: The type of the measure report 2.16.840.1.113883.4.642.1.779
measure-scoring MeasureScoring: The scoring type of the measure 2.16.840.1.113883.4.642.1.768
measure-type MeasureType: The type of measure (includes codes from 2.16.840.1.113883.1.11.20368) 2.16.840.1.113883.4.642.1.770
measurement-principle MeasmntPrinciple: Different measurement principle supported by the device. 2.16.840.1.113883.4.642.1.627
med-admin-perform-function MedicationAdministrationPerformerFunction: A code describing the role an individual played in administering the medication 2.16.840.1.113883.4.642.1.350
med-dispense-perform-function MedicationDispensePerformerFunction: A code describing the role an individual played in dispensing a medication 2.16.840.1.113883.4.642.1.358
med-dispense-status-reason MedicationDispenseStatusReason: A code describing why a dispense was not performed 2.16.840.1.113883.4.642.1.356
med-request-status-reason MedicationRequestStatusReason: Identifies the reasons for a given status 2.16.840.1.113883.4.642.1.366
media-modality Media Modality: Detailed information about the type of the image - its kind, purpose, or the kind of equipment used to generate it. 2.16.840.1.113883.4.642.1.1002
medication-admin-category MedicationAdministrationCategory: A coded concept describing where the medication administered is expected to occur 2.16.840.1.113883.4.642.1.348
medication-admin-status MedicationAdministrationStatus: A set of codes indicating the current status of a MedicationAdministration. 2.16.840.1.113883.4.642.1.341
medication-dispense-category MedicationDispenseCategory: A code describing where the dispensed medication is expected to be consumed or administered 2.16.840.1.113883.4.642.1.354
medication-dispense-status MedicationDispenseStatus: A coded concept specifying the state of the dispense event. 2.16.840.1.113883.4.642.1.352
medication-request-category MedicationRequestCategory: A 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. 2.16.840.1.113883.4.642.1.364
medication-request-intent MedicationRequestIntent: The kind of medication order 2.16.840.1.113883.4.642.1.362
medication-request-status MedicationRequestStatus: A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription 2.16.840.1.113883.4.642.1.360
medication-statement-category MedicationStatementCategory: A coded concept identifying where the medication included in the MedicationStatement is expected to be consumed or administered 2.16.840.1.113883.4.642.1.371
medication-statement-status MedicationStatementStatus: A coded concept indicating the current status of a MedicationStatement. 2.16.840.1.113883.4.642.1.368
medication-statement-taken MedicationStatementTaken: A coded concept identifying level of certainty if patient has taken or has not taken the medication 2.16.840.1.113883.4.642.1.373
medication-status MedicationStatus: A coded concept defining if the medication is in active use 2.16.840.1.113883.4.642.1.377
medicationKnowledge-character MedicationCharacteristic: A coded concept defining the characteristic types of a medication 2.16.840.1.113883.4.642.1.1033
medicationKnowledge-package MedicationPackageType: A coded concept defining the type of packaging of a medication 2.16.840.1.113883.4.642.1.1035
medicationKnowledge-status MedicationKnowledgeStatus: A coded concept defining if the medication is in active use 2.16.840.1.113883.4.642.1.1031
message-events N MessageEvent: One of the message events defined as part of this version of FHIR.
message-reasons-encounter Example Message Reason Codes: Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. 2.16.840.1.113883.4.642.1.379
message-significance-category MessageSignificanceCategory: The impact of the content of a message. 2.16.840.1.113883.4.642.1.189
message-transport N MessageTransport: The protocol used for message transport. 2.16.840.1.113883.4.642.1.185
messageheader-response-request messageheader-response-request: HL7-defined table of codes which identify conditions under which acknowledgments are required to be returned in response to a message. 2.16.840.1.113883.4.642.1.925
metric-calibration-state DeviceMetricCalibrationState: Describes the state of a metric calibration. 2.16.840.1.113883.4.642.1.653
metric-calibration-type DeviceMetricCalibrationType: Describes the type of a metric calibration. 2.16.840.1.113883.4.642.1.651
metric-category DeviceMetricCategory: Describes the category of the metric. 2.16.840.1.113883.4.642.1.649
metric-color DeviceMetricColor: Describes the typical color of representation. 2.16.840.1.113883.4.642.1.655
metric-operational-status DeviceMetricOperationalStatus: Describes the operational status of the DeviceMetric. 2.16.840.1.113883.4.642.1.647
missingtoothreason Missing Tooth Reason Codes: This value set includes sample Missing Tooth Reason codes. 2.16.840.1.113883.4.642.1.535
modifiers Modifier type Codes: This value set includes sample Modifier type codes. 2.16.840.1.113883.4.642.1.537
name-assembly-order HumanNameAssemblyOrder: A code that represents the preferred display order of the components of a human name 2.16.840.1.113883.4.642.1.914
name-use NameUse: The use of a human name 2.16.840.1.113883.4.642.1.66
namingsystem-identifier-type NamingSystemIdentifierType: Identifies the style of unique identifier used to identify a namespace. 2.16.840.1.113883.4.642.1.493
namingsystem-type NamingSystemType: Identifies the purpose of the naming system. 2.16.840.1.113883.4.642.1.491
narrative-status NarrativeStatus: The status of a resource narrative 2.16.840.1.113883.4.642.1.56
network-type AuditEventAgentNetworkType: The type of network access point of this agent in the audit event 2.16.840.1.113883.4.642.1.457
note-type NoteType: The presentation types of notes. 2.16.840.1.113883.4.642.1.16
object-role AuditEventEntityRole: Code representing the role the entity played in the audit event 2.16.840.1.113883.4.642.1.461
observation-category N Observation Category Codes: Observation Category codes. 2.16.840.1.113883.4.642.1.404
observation-statistics StatisticsCode: The statistical operation parameter -"statistic" codes 2.16.840.1.113883.4.642.1.406
observation-status N ObservationStatus: Codes providing the status of an observation. 2.16.840.1.113883.4.642.1.401
operation-kind N OperationKind: Whether an operation is a normal operation or a query. 2.16.840.1.113883.4.642.1.507
operation-outcome Operation Outcome Codes: Operation Outcome codes used by FHIR test servers (see Implementation file translations.xml) 2.16.840.1.113883.4.642.1.413
operation-parameter-use N OperationParameterUse: Whether an operation parameter is an input or an output parameter. 2.16.840.1.113883.4.642.1.509
operational-status DeviceComponentOperationalStatus: Codes representing the current status of the device - on, off, suspended, etc. 2.16.840.1.113883.4.642.1.629
organization-role OrganizationRole: This example value set defines a set of codes that can be used to indicate the role of one Organization in relation to another. 2.16.840.1.113883.4.642.1.881
organization-type OrganizationType: This example value set defines a set of codes that can be used to indicate a type of organization. 2.16.840.1.113883.4.642.1.415
orientation-type orientationType: Type for orientation 2.16.840.1.113883.4.642.1.988
parameter-group DeviceComponentParameterGroup: Codes identifying groupings of parameters; e.g. Cardiovascular. 2.16.840.1.113883.4.642.1.633
participant-type ParticipantType: This value set defines a set of codes that can be used to indicate how an individual participates in an encounter. 2.16.840.1.113883.4.642.1.251
participantrequired ParticipantRequired: Is the Participant required to attend the appointment. 2.16.840.1.113883.4.642.1.489
participationstatus ParticipationStatus: The Participation status of an appointment. 2.16.840.1.113883.4.642.1.487
payeetype Claim Payee Type Codes: This value set includes sample Payee Type codes. 2.16.840.1.113883.4.642.1.32
payment-adjustment-reason Payment Adjustment Reason Codes: This value set includes smattering of Payment Adjustment Reason codes. 2.16.840.1.113883.4.642.1.601
payment-type Payment Type Codes: This value set includes sample Payment Type codes. 2.16.840.1.113883.4.642.1.642
paymentstatus Payment Status Codes: This value set includes a sample set of Payment Status codes. 2.16.840.1.113883.4.642.1.644
plan-definition-type PlanDefinitionType: The type of PlanDefinition 2.16.840.1.113883.4.642.1.798
policyholder-relationship Policyholder Relationship Codes: This value set includes codes for the relationship between the Policyholder and the Beneficiary (insured/covered party/patient).. 2.16.840.1.113883.4.642.1.522
practitioner-role PractitionerRole: This example value set defines a set of codes that can be used to indicate the role of a Practitioner. 2.16.840.1.113883.4.642.1.440
practitioner-specialty PractitionerSpecialty: This example value set defines a set of codes that can be used to indicate the specialty of a Practitioner. 2.16.840.1.113883.4.642.1.442
procedure-progress-status-code Procedure Progress Status Codes: This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the procedure performance process. 2.16.840.1.113883.4.642.1.947
processoutcomecodes Process Outcome Codes: This value set includes sample Process Outcome codes. 2.16.840.1.113883.4.642.1.692
processpriority Process Priority Codes: This value set includes the financial processing priority codes. 2.16.840.1.113883.4.642.1.553
product-category BiologicallyDerivedProductCategory: Biologically Derived Product Category 2.16.840.1.113883.4.642.1.901
product-plan-type ProductPlanType: This example value set defines a set of codes that can be used to indicate a type of product plan. 2.16.840.1.113883.4.642.1.871
product-status BiologicallyDerivedProductStatus: Biologically Derived Product Status 2.16.840.1.113883.4.642.1.903
product-storage-scale BiologicallyDerivedProductStorageScale: BiologicallyDerived Product Storage Scale 2.16.840.1.113883.4.642.1.905
property-representation PropertyRepresentation: How a property is represented when serialized. 2.16.840.1.113883.4.642.1.88
provenance-entity-role ProvenanceEntityRole: How an entity was used in an activity. 2.16.840.1.113883.4.642.1.437
provenance-participant-type ProvenanceParticipantType: The type of participation a provenance participant. 2.16.840.1.113883.4.642.1.1004
publication-status N PublicationStatus: The lifecycle status of an artifact. 2.16.840.1.113883.4.642.1.4
quality-type qualityType: Type for quality report 2.16.840.1.113883.4.642.1.229
quantity-comparator QuantityComparator: How the Quantity should be understood and represented. 2.16.840.1.113883.4.642.1.60
question-max-occurs MaxOccurs: Flags an element as having unlimited repetitions 2.16.840.1.113883.4.642.1.930
questionnaire-answers-status QuestionnaireResponseStatus: Lifecycle status of the questionnaire response. 2.16.840.1.113883.4.642.1.448
questionnaire-display-category Questionnaire Text Categories: Codes defining the purpose of a Questionnaire item of type 'text'. 2.16.840.1.113883.4.642.1.936
questionnaire-enable-behavior EnableWhenBehavior: Controls how multiple enableWhen values are interpreted - whether all or any must be true 2.16.840.1.113883.4.642.1.1008
questionnaire-enable-operator QuestionnaireItemOperator: The criteria by which a question is enabled 2.16.840.1.113883.4.642.1.1006
questionnaire-item-control Questionnaire Item UI Control Codes: Starter set of user interface control/display mechanisms that might be used when rendering an item in a questionnaire. 2.16.840.1.113883.4.642.1.932
questionnaire-usage-mode QuestionnaireItemUsageMode: Identifies the modes of usage of a questionnaire that should enable a particular questionnaire item 2.16.840.1.113883.4.642.1.938
reaction-event-certainty AllergyIntoleranceCertainty: Statement about the degree of clinical certainty that a specific substance was the cause of the manifestation in a reaction event. 2.16.840.1.113883.4.642.1.943
reaction-event-severity AllergyIntoleranceSeverity: Clinical assessment of the severity of a reaction event as a whole, potentially considering multiple different manifestations. 2.16.840.1.113883.4.642.1.136
reason-medication-given Reason Medication Given Codes: This value set is provided as an example. The value set to instantiate this attribute should be drawn from a robust terminology code system that consists of or contains concepts to support the medication process. 2.16.840.1.113883.4.642.1.345
reason-medication-not-given SNOMED CT Reason Medication Not Given Codes: This value set includes all medication refused, medication not administered, and non-administration of necessary drug or medicine codes from SNOMED CT - provided as an exemplar value set. 2.16.840.1.113883.4.642.1.343
recommendation-strength StrengthOfRecommendationRating: A rating system that describes the strength of the recommendation, such as the GRADE, DynaMed, or HGPS systems 2.16.840.1.113883.4.642.1.977
reference-handling-policy N ReferenceHandlingPolicy: A set of flags that defines how references are supported. 2.16.840.1.113883.4.642.1.203
reference-version-rules ReferenceVersionRules: Whether a reference needs to be version specific or version independent, or whether either can be used 2.16.840.1.113883.4.642.1.90
referencerange-meaning N Observation Reference Range Meaning Codes: This value set defines a set of codes that can be used to indicate the meaning/use of a reference range for a particular target population. 2.16.840.1.113883.4.642.1.398
rejection-criteria RejectionCriterion: Criterion for rejection of the specimen by laboratory 2.16.840.1.113883.4.642.1.857
related-artifact-type RelatedArtifactType: The type of relationship to the related artifact 2.16.840.1.113883.4.642.1.100
relation-type EntryDefinitionRelationType: The type of relations between entries 2.16.840.1.113883.4.642.1.1029
relationship Beneficiary Relationship Codes: This value set includes the Patient to subscriber relationship codes. 2.16.840.1.113883.4.642.1.36
remittance-outcome Claim Processing Codes: This value set includes Claim Processing Outcome codes. 2.16.840.1.113883.4.642.1.14
report-action-result-codes TestReportActionResult: The results of executing an action. 2.16.840.1.113883.4.642.1.721
report-participant-type TestReportParticipantType: The type of participant. 2.16.840.1.113883.4.642.1.723
report-result-codes TestReportResult: The reported execution result. 2.16.840.1.113883.4.642.1.719
report-status-codes TestReportStatus: The current status of the test report. 2.16.840.1.113883.4.642.1.725
repository-type repositoryType: Type for access of external URI 2.16.840.1.113883.4.642.1.231
request-intent RequestIntent: Codes indicating the degree of authority/intentionality associated with a request 2.16.840.1.113883.4.642.1.114
request-priority RequestPriority: Identifies the level of importance to be assigned to actioning the request 2.16.840.1.113883.4.642.1.116
request-status RequestStatus: Codes identifying the lifecycle stage of a request 2.16.840.1.113883.4.642.1.112
research-study-objective-type ResearchStudyObjectiveType: Codes for the kind of study objective 2.16.840.1.113883.4.642.1.824
research-study-phase ResearchStudyPhase: Codes for the stage in the progression of a therapy from initial experimental use in humans in clinical trials to post-market evaluation. 2.16.840.1.113883.4.642.1.822
research-study-prim-purp-type ResearchStudyPrimaryPurposeType: Codes for the main intent of the study 2.16.840.1.113883.4.642.1.828
research-study-reason-stopped ResearchStudyReasonStopped: Codes for why the study ended prematurely 2.16.840.1.113883.4.642.1.826
research-study-status ResearchStudyStatus: Codes that convey the current status of the research study 2.16.840.1.113883.4.642.1.820
research-subject-status ResearchSubjectStatus: Indicates the progression of a study subject through a study 2.16.840.1.113883.4.642.1.830
resource-aggregation-mode AggregationMode: How resource references can be aggregated. 2.16.840.1.113883.4.642.1.86
resource-slicing-rules SlicingRules: How slices are interpreted when evaluating an instance. 2.16.840.1.113883.4.642.1.84
resource-status Canonical Status Codes for FHIR Resources: The master set of status codes used throughout FHIR. All status codes are mapped to one of these codes.
resource-type-link PayeeResourceType: The type of payee Resource 2.16.840.1.113883.4.642.1.615
resource-types N ResourceType: One of the resource types defined as part of this version of FHIR.
resource-validation-mode ResourceValidationMode: Codes indicating the type of validation to perform 2.16.840.1.113883.4.642.1.119
response-code ResponseType: The kind of response to a message 2.16.840.1.113883.4.642.1.381
restful-capability-mode N RestfulCapabilityMode: The mode of a RESTful capability statement. 2.16.840.1.113883.4.642.1.177
restful-interaction N FHIR Restful Interactions: The set of interactions defined by the RESTful part of the FHIR specification.
restful-security-service N RestfulSecurityService: Types of security services used with FHIR. 2.16.840.1.113883.4.642.1.179
risk-probability Risk Probability: Codes representing the likelihood of a particular outcome in a risk assessment. 2.16.840.1.113883.4.642.1.451
search-comparator SearchComparator: What Search Comparator Codes are supported in search 2.16.840.1.113883.4.642.1.638
search-entry-mode N SearchEntryMode: Why an entry is in the result set - whether it's included as a match or because of an _include requirement. 2.16.840.1.113883.4.642.1.623
search-modifier-code SearchModifierCode: A supported modifier for a search parameter. 2.16.840.1.113883.4.642.1.640
search-param-type N SearchParamType: Data types allowed to be used for search parameters. 2.16.840.1.113883.4.642.1.12
search-xpath-usage XPathUsageType: How a search parameter relates to the set of elements returned by evaluating its xpath query. 2.16.840.1.113883.4.642.1.636
security-source-type Audit Event Source Type: The type of process where the audit event originated from. 2.16.840.1.113883.4.642.1.467
sequence-type sequenceType: Type if a sequence -- DNA, RNA, or amino acid sequence 2.16.840.1.113883.4.642.1.220
service-category ServiceCategory: This value set defines an example set of codes that can be used to classify groupings of service-types/specialties. 2.16.840.1.113883.4.642.1.517
service-provision-conditions ServiceProvisionConditions: The code(s) that detail the conditions under which the healthcare service is available/offered. 2.16.840.1.113883.4.642.1.515
service-referral-method ReferralMethod: The methods of referral can be used when referring to a specific HealthCareService resource. 2.16.840.1.113883.4.642.1.511
service-type ServiceType: This value set defines an example set of codes of service-types. 2.16.840.1.113883.4.642.1.519
sid/ex-icd-10-procedures ICD-10 Procedure Codes: This value set includes sample ICD-10 Procedure codes. 2.16.840.1.113883.4.642.1.575
slotstatus SlotStatus: The free/busy status of the slot. 2.16.840.1.113883.4.642.1.483
smart-capabilities SmartCapabilities: Codes that define what the server is capable of 2.16.840.1.113883.4.642.1.1019
sort-direction SortDirection: The possible sort directions, ascending or descending 2.16.840.1.113883.4.642.1.980
spdx-license SPDXLicense: The license that applies to an Implementation Guide (using an SPDX license Identifiers, or 'not-open-source'). The binding is required but new SPDX license Identifiers are allowed to be used ( 2.16.840.1.113883.4.642.1.1027
special-values SpecialValues: A set of generally useful codes defined so they can be included in value sets. 2.16.840.1.113883.4.642.1.10
specification-type DeviceSpecificationSpecType: Codes for device specification types such as serial number, part number, hardware revision, software revision, etc. 2.16.840.1.113883.4.642.1.631
specimen-contained-preference SpecimenContainedPreference: Degree of preference of a type of conditioned specimen 2.16.840.1.113883.4.642.1.853
specimen-status SpecimenStatus: Codes providing the status/availability of a specimen. 2.16.840.1.113883.4.642.1.472
strand-type strandType: Type for strand 2.16.840.1.113883.4.642.1.986
structure-definition-kind N StructureDefinitionKind: Defines the type of structure that a definition is describing. 2.16.840.1.113883.4.642.1.669
subscription-channel-type SubscriptionChannelType: The type of method used to execute a subscription. 2.16.840.1.113883.4.642.1.501
subscription-status SubscriptionStatus: The status of a subscription. 2.16.840.1.113883.4.642.1.503
subscription-tag SubscriptionTag: Tags to put on a resource after subscriptions have been sent. 2.16.840.1.113883.4.642.1.505
substance-category Substance Category Codes: Substance category codes 2.16.840.1.113883.4.642.1.477
substance-status FHIRSubstanceStatus: A code to indicate if the substance is actively used 2.16.840.1.113883.4.642.1.475
supply-item-type Supply Item Type: This value sets refers to a specific supply item. 2.16.840.1.113883.4.642.1.703
supply-kind Supply Type: This value sets refers to a Category of supply. 2.16.840.1.113883.4.642.1.694
supplydelivery-status SupplyDeliveryStatus: Status of the supply delivery. 2.16.840.1.113883.4.642.1.701
supplyrequest-reason SupplyRequestReason: The reason why the supply item was requested 2.16.840.1.113883.4.642.1.698
supplyrequest-status SupplyRequestStatus: Status of the supply request 2.16.840.1.113883.4.642.1.696
task-performer-type TaskPerformerType: The type(s) of task performers allowed 2.16.840.1.113883.4.642.1.789
task-status TaskStatus: The current status of the task. 2.16.840.1.113883.4.642.1.791
testscript-operation-codes TestScriptOperationCode: This value set defines a set of codes that are used to indicate the supported operations of a testing engine or tool. 2.16.840.1.113883.4.642.1.705
testscript-profile-destination-types TestScriptProfileDestinationType: This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript. 2.16.840.1.113883.4.642.1.715
testscript-profile-origin-types TestScriptProfileOriginType: This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the origin within a TestScript. 2.16.840.1.113883.4.642.1.713
transaction-mode TransactionMode: A code that indicates how transactions are supported. 2.16.840.1.113883.4.642.1.193
trigger-type TriggerType: The type of trigger 2.16.840.1.113883.4.642.1.104
type-derivation-rule N TypeDerivationRule: How a type relates to its baseDefinition. 2.16.840.1.113883.4.642.1.674
udi-entry-type UDIEntryType: Codes to identify how UDI data was entered 2.16.840.1.113883.4.642.1.212
unknown-content-code UnknownContentCode: A code that indicates whether an application accepts unknown elements or extensions when reading resources. 2.16.840.1.113883.4.642.1.197
usage-context-type UsageContextType: A code that specifies a type of context being specified by a usage context 2.16.840.1.113883.4.642.1.102
usersession-status UserSessionStatus: The status of the user session 2.16.840.1.113883.4.642.1.863
usersession-status-source UserSessionStatusSource: The source of the status of the user session 2.16.840.1.113883.4.642.1.865
variant-state sequenceStatus: Codes providing the status of the variant test result 2.16.840.1.113883.4.642.1.218
versioning-policy N ResourceVersionPolicy: How the system supports versioning for a resource. 2.16.840.1.113883.4.642.1.191
vision-base-codes VisionBase: A coded concept listing the base codes. 2.16.840.1.113883.4.642.1.663
vision-eye-codes VisionEyes: A coded concept listing the eye codes. 2.16.840.1.113883.4.642.1.661
w3c-provenance-activity-type W3cProvenanceActivityType: This value set includes W3C PROV Data Model Activity concepts, which are treated as codes in this valueset. Some adaptations were made to make these concepts suitable values for the Provenance.activity element. Coded concepts are from PROV-DM and the display names are their counterparts in PROV-N (human readable notation syntax specification).[code system OID: and]
Name (URI =
AcknowledgementCondition The codes identify the conditions under which accept acknowledgements are required to be returned in response to this message. Note that accept acknowledgement address two different issues at the same time: reliable transport as well as syntactical correctness2.16.840.1.113883.5.1050
AcknowledgementDetailCode OpenIssue: Missing description.2.16.840.1.113883.5.1100
AcknowledgementDetailType A code identifying the specific message to be provided. Discussion: A textual value may be specified as the print name, or for non-coded messages, as the original text. Examples: 'Required attribute xxx is missing', 'System will be unavailable March 19 from 0100 to 0300'2.16.840.1.113883.5.1082
AcknowledgementType This attribute contains an acknowledgement code as described in the HL7 message processing rules. OpenIssue: Description was copied from attribute and needs to be improved to be appropriate for a code system.2.16.840.1.113883.5.18
ActClass**** MISSING DEFINITIONS ****2.16.840.1.113883.5.6
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.2.16.840.1.113883.5.4
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.2.16.840.1.113883.5.1114
ActInvoiceElementModifier Processing consideration and clarification codes.2.16.840.1.113883.5.1051
ActMood OpenIssue: In Ballot 2009May, a strong Negative vote was lodged against several of the concept definitions in the vocabulary used for Act.moodCode. The vote was found "Persuasive With Mod", with the understanding that M and M would undertake a detailed review of these concept definitions for a future release of the RIM.2.16.840.1.113883.5.1001
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.2.16.840.1.113883.5.7
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".2.16.840.1.113883.5.8
ActRelationshipCheckpoint**** MISSING DEFINITIONS ****2.16.840.1.113883.5.10
ActRelationshipJoin**** MISSING DEFINITIONS ****2.16.840.1.113883.5.12
ActRelationshipSplit**** MISSING DEFINITIONS ****2.16.840.1.113883.5.13
ActRelationshipSubset <ns1:p>Used to indicate that the target of the relationship will be a filtered subset of the total related set of targets.</ns1:p><ns1:p>Used when there is a need to limit the number of components to the first, the last, the next, the total, the average or some other filtered or calculated subset.</ns1:p>2.16.840.1.113883.5.1099
ActRelationshipType The source is an excerpt from the target.2.16.840.1.113883.5.1002
ActSite An anatomical location on an organism which can be the focus of an act.2.16.840.1.113883.5.1052
ActStatus Codes representing the defined possible states of an Act, as defined by the Act class state machine.2.16.840.1.113883.5.14
ActUSPrivacyLaw A jurisdictional mandate in the US relating to privacy. Deprecation Comment: Content moved to ActCode under _ActPrivacyLaw; use that instead.2.16.840.1.113883.5.1138
ActUncertainty OpenIssue: Missing Description2.16.840.1.113883.5.1053
AddressPartType Description: Code that specifies whether an address part names the street, city, country, postal code, post box, etc. Discussion: The hierarchical nature of these concepts shows composition. E.g. "Street Name" is part of "Street Address Line"2.16.840.1.113883.5.16
AddressUse Codes that provide guidance around the circumstances in which a given address should be used.2.16.840.1.113883.5.1119
AdministrativeGender The gender of a person used for adminstrative purposes (as opposed to clinical gender)2.16.840.1.113883.5.1
AmericanIndianAlaskaNativeLanguages American Indian and Alaska Native languages currently being used in the United States.2.16.840.1.113883.5.1054
Calendar**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1055
CalendarCycle Calendar cycle identifiers2.16.840.1.113883.5.9
CalendarType**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1017
Charset Internet Assigned Numbers Authority (IANA) Charset Types2.16.840.1.113883.5.21
CodingRationale Identifies how to interpret the instance of the code, codeSystem value in a set of translations. Since HL7 (or a government body) may mandate that codes from certain code systems be sent in conformant messages, other synonyms that are sent in the translation set need to be distinguished among the originally captured source, the HL7 specified code, or some future role. When this code is NULL, it indicates that the translation is an undefined type. When valued, this property must contain one of the following values: SRC - Source (or original) code HL7 - HL7 Specified or Mandated SH - both HL7 mandated and the original code (precoordination) There may be additional values added to this value set as we work through the use of codes in messages and determine other Use Cases requiring special interpretation of the translations.2.16.840.1.113883.5.1074
CommunicationFunctionType Describes the type of communication function that the associated entity plays in the associated transmission.2.16.840.1.113883.5.1056
CompressionAlgorithm**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1009
Confidentiality A set of codes specifying the security classification of acts and roles in accordance with the definition for concept domain "Confidentiality".2.16.840.1.113883.5.25
ContainerCap The type of cap associated with a container2.16.840.1.113883.5.26
ContainerSeparator A material in a blood collection container that facilites the separation of of blood cells from serum or plasma2.16.840.1.113883.5.27
ContentProcessingMode Description: Identifies the order in which content should be processed.2.16.840.1.113883.5.1110
ContextControl A code that specifies how an ActRelationship or Participation contributes to the context of an Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see also attributes Participation.contextControlCode, ActRelationship.contextControlCode, ActRelationship.contextConductionInd).2.16.840.1.113883.5.1057
DataOperation**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1123
DeviceAlertLevel Domain values for the Device.Alert_levelCode2.16.840.1.113883.5.31
DocumentCompletion Identifies the current completion state of a clinical document.2.16.840.1.113883.5.33
DocumentStorage Identifies the storage status of a document.2.16.840.1.113883.5.34
EducationLevel Years of education that a person has completed2.16.840.1.113883.5.1077
EmployeeJobClass**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1059
EncounterAdmissionSource**** MISSING DEFINITIONS ****2.16.840.1.113883.5.37
EncounterSpecialCourtesy**** MISSING DEFINITIONS ****2.16.840.1.113883.5.40
EntityClass Classifies the Entity class and all of its subclasses. The terminology is hierarchical. At the top is this HL7-defined domain of high-level categories (such as represented by the Entity subclasses). Each of these terms must be harmonized and is specializable. The value sets beneath are drawn from multiple, frequently external, domains that reflect much more fine-grained typing.2.16.840.1.113883.5.41
EntityCode OpenIssue: Missing description.2.16.840.1.113883.5.1060
EntityDeterminer EntityDeterminer in natural language grammar is the class of words that comprises articles, demonstrative pronouns, and quantifiers. In the RIM, determiner is a structural code in the Entity class to distinguish whether any given Entity object stands for some, any one, or a specific thing.2.16.840.1.113883.5.30
EntityHandling**** MISSING DEFINITIONS ****2.16.840.1.113883.5.42
EntityNamePartQualifier OpenIssue: Needs description2.16.840.1.113883.5.43
EntityNamePartQualifierR2 Description: The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records.2.16.840.1.113883.5.1122
EntityNamePartType**** MISSING DEFINITIONS ****2.16.840.1.113883.5.44
EntityNamePartTypeR2 Description: Indicates whether the name part is a given name, family name, prefix, suffix, etc.2.16.840.1.113883.5.1121
EntityNameUse**** MISSING DEFINITIONS ****2.16.840.1.113883.5.45
EntityNameUseR2 Description: A set of codes advising a system or user which name in a set of names to select for a given purpose.2.16.840.1.113883.5.1120
EntityRisk Kinds of risks associated with the handling of the material..2.16.840.1.113883.5.46
EntityStatus Codes representing the defined possible states of an Entity, as defined by the Entity class state machine.2.16.840.1.113883.5.1061
EquipmentAlertLevel**** MISSING DEFINITIONS ****2.16.840.1.113883.5.49
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.2.16.840.1.113883.5.50
ExposureMode Code for the mechanism by which the exposure agent was exchanged or potentially exchanged by the participants involved in the exposure.2.16.840.1.113883.5.1113
GTSAbbreviation Open Issue: It appears that the printnames are suboptimal and should be improved for many of the existing codes.2.16.840.1.113883.5.1022
GenderStatus**** MISSING DEFINITIONS ****2.16.840.1.113883.5.51
HL7UpdateMode The possible modes of updating that occur when an attribute is received by a system that already contains values for that attribute.2.16.840.1.113883.5.57
HtmlLinkType HtmlLinkType values are drawn from HTML 4.0 and describe the relationship between the current document and the anchor that is the target of the link2.16.840.1.113883.5.58
IdentifierReliability Specifies the reliability with which the identifier is known. This attribute MAY be used to assist with identifier matching algorithms.2.16.840.1.113883.5.1117
IdentifierScope Description: Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II.2.16.840.1.113883.5.1116
IntegrityCheckAlgorithm**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1010
LanguageAbilityMode A value representing the method of expression of the language. Example: Expressed spoken, expressed written, expressed signed, received spoken, received written, received signed. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.5.60
LanguageAbilityProficiency A value representing the level of proficiency in a language. Example: Excellent, good, fair, poor. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.5.61
LivingArrangement A code depicting the living arrangements of a person2.16.840.1.113883.5.63
LocalMarkupIgnore Tells a receiver to ignore just the local markup tags (local_markup, local_header, local_attr) when value="markup", or to ignore the local markup tags and all contained content when value="all"2.16.840.1.113883.5.65
LocalRemoteControlState**** MISSING DEFINITIONS ****2.16.840.1.113883.5.66
ManagedParticipationStatus Codes representing the defined possible states of a Managed Participation, as defined by the Managed Participation class state machine.2.16.840.1.113883.5.1062
MapRelationship The closeness or quality of the mapping between the HL7 concept (as represented by the HL7 concept identifier) and the source coding system. The values are patterned after the similar relationships used in the UMLS Metathesaurus. Because the HL7 coding sy2.16.840.1.113883.5.67
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.2.16.840.1.113883.5.2
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.2.16.840.1.113883.5.1083
ModifyIndicator**** MISSING DEFINITIONS ****2.16.840.1.113883.5.81
NullFlavor A collection of codes specifying why a valid value is not present.2.16.840.1.113883.5.1008
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).2.16.840.1.113883.5.83
ObservationMethod A code that provides additional detail about the means or technique used to ascertain the observation. Examples: Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc. OpenIssue: Description copied from Concept Domain of same name. Must be verified. Note that the Domain has a full discussion about use of the attribute and constraining that is not appropriate for the code system description. Needs to be improved.2.16.840.1.113883.5.84
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..2.16.840.1.113883.5.1063
ParticipationFunction This code is used to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE).2.16.840.1.113883.5.88
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.2.16.840.1.113883.5.1064
ParticipationSignature A set of codes specifying whether and how the participant has attested his participation through a signature and or whether such a signature is needed. Examples: A surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. (See also: Participation.signatureText.)2.16.840.1.113883.5.89
ParticipationType**** MISSING DEFINITIONS ****2.16.840.1.113883.5.90
PatientImportance Patient VIP code2.16.840.1.113883.5.1075
PaymentTerms Describes payment terms for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor of an invoice.2.16.840.1.113883.5.91
PersonDisabilityType A code identifying a person's disability.2.16.840.1.113883.5.93
ProbabilityDistributionType**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1020
ProcessingID Codes used to specify whether a message is part of a production, training, or debugging system.2.16.840.1.113883.5.100
ProcessingMode**** MISSING DEFINITIONS ****2.16.840.1.113883.5.101
QueryParameterValue The domain of coded values used as parameters within QueryByParameter queries.2.16.840.1.113883.5.1096
QueryPriority**** MISSING DEFINITIONS ****2.16.840.1.113883.5.102
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.2.16.840.1.113883.5.1112
QueryResponse A code classifying the general nature of the response to a given query. Includes whether or not data was found, or whether an error occurred.2.16.840.1.113883.5.1067
QueryStatusCode A code specifying the state of the Query.2.16.840.1.113883.5.103
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.2.16.840.1.113883.5.104
RelationalOperator**** MISSING DEFINITIONS ****2.16.840.1.113883.5.105
RelationshipConjunction**** MISSING DEFINITIONS ****2.16.840.1.113883.5.106
ReligiousAffiliation Assigment of spiritual faith affiliation2.16.840.1.113883.5.1076
ResponseLevel Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include2.16.840.1.113883.5.108
ResponseModality Defines the timing and grouping of the response instances. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.5.109
ResponseMode Specifies the mode, immediate versus deferred or queued, by which a receiver should communicate its receiver responsibilities.2.16.840.1.113883.5.1126
RoleClass Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role. The role hierarchy stems from three core concepts, or abstract domains: RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity. RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity. RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between: RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity. RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into: RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement. Personal relationship which inks two people in a personal relationship. The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept. OpenIssue: Description copied from Concept Domain of same name. Must be verified.2.16.840.1.113883.5.110
RoleCode A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes.2.16.840.1.113883.5.111
RoleLinkStatus Description: Codes representing possible states of a RoleLink, as defined by the RoleLink class state machine.2.16.840.1.113883.5.1137
RoleLinkType**** MISSING DEFINITIONS ****2.16.840.1.113883.5.107
RoleStatus Codes representing the defined possible states of an Role, as defined by the Role class state machine.2.16.840.1.113883.5.1068
RouteOfAdministration The path the administered medication takes to get into the body or into contact with the body.2.16.840.1.113883.5.112
Sequencing Specifies sequence of sort order.2.16.840.1.113883.5.113
SetOperator**** MISSING DEFINITIONS ****2.16.840.1.113883.5.1069
SpecimenType**** MISSING DEFINITIONS ****2.16.840.1.113883.5.129
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.2.16.840.1.113883.5.1071
TableCellHorizontalAlign These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.5.131
TableCellScope These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.5.132
TableCellVerticalAlign These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.5.133
TableFrame These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.5.134
TableRules These values are defined within the XHTML 4.0 Table Model2.16.840.1.113883.5.136
TargetAwareness**** MISSING DEFINITIONS ****2.16.840.1.113883.5.137
TelecommunicationCapabilities Description: Concepts that define the telecommunication capabilities of a particular device. Used to identify the expected capabilities to be found at a particular telecommunication address.2.16.840.1.113883.5.1118
TimingEvent**** MISSING DEFINITIONS ****2.16.840.1.113883.5.139
TransmissionRelationshipTypeCode Description: A code specifying the meaning and purpose of every TransmissionRelationship instance. Each of its values implies specific constraints to what kinds of Transmission objects can be related and in which way.2.16.840.1.113883.5.1111
VaccineManufacturer The manufacturer of a vaccine.2.16.840.1.113883.5.144
hl7Realm Description: Coded concepts representing Binding Realms (used for Context Binding of terminology in HL7 models) and/or Namespace Realms (used to help ensure unique identification of HL7 artifacts). This code system is partitioned into three sections: Affiliate realms, Binding realms and Namespace realms. All affiliate realm codes may automatically be used as both binding realms and namespace realms. Furthermore, affiliate realms are the only realms that have authority over the creation of binding realms. (Note that 'affiliate' includes the idea of both international affiliates and the HL7 International organization.) All other codes must be associated with an owning affiliate realm and must appear as a specialization of _BindingRealm or _NamespaceRealm. For affiliates whose concepts align with nations, the country codes from ISO 3166-1 2-character alpha are used for the code when possible so these codes should not be used for other realm types. It is recommended that binding realm and namespace codes submitted by affiliates use the realm code as a prefix to avoid possible collisions with ISO codes. However, tooling does not currently support namepace realm codes greater than 2 characters. Open Issue: The name of the concept property "owningAffiliate" should be changed to better reflect that the property value is the human readable name of the organizational entity that manages the Realm identified by the Realm Code. Open Issue: In spite of the inability of tooling to process codes longer than 2 characters, there is at least one realm codes ('SOA') that was added that is 3 characters in length.2.16.840.1.113883.5.1124
hl7V3Conformance Description: Identifies allowed codes for HL7aTMs v3 conformance property.2.16.840.1.113883.5.1125
orderableDrugForm OpenIssue: Missing description.2.16.840.1.113883.5.85
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.2.16.840.1.113883.5.1070
URI (all prefixed with
0001Administrative Sex
0002Marital Status
0003Event Type
0004Patient Class
0006ReligionVersion Dependent. Use one of:
0007Admission Type
0008Acknowledgment code
0009Ambulatory Status
0017Transaction Type
0023Admit Source
0038Order status
0043Condition Code
0048What subject filter
0052Diagnosis Type
0061Check Digit Scheme
0062Event Reason
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
0126Quantity Limited Request
0127Allergen Type
0128Allergy Severity
0130Visit User Code
0131Contact Role
0133Procedure Practitioner Identifier Code Type
0135Assignment of Benefits
0136Yes/no Indicator
0137Mail Claim Party
0140Military Service
0141Military Rank/Grade
0142Military Status
0144Eligibility Source
0145Room Type
0146Amount Type
0147Policy Type
0148Money or Percentage Indicator
0149Day Type
0150Certification Patient Type
0153Value Code
0155Accept/Application Acknowledgment Conditions
0156Which date/time qualifier
0157Which date/time status qualifier
0158Date/time selection qualifier
0159Diet Code Specification Type
0160Tray Type
0161Allow Substitution
0162Route of Administration
0163Body Site
0164Administration Device
0165Administration Method
0166RX Component Type
0167Substitution Status
0168Processing Priority
0169Reporting Priority
0170Derived Specimen
0173Coordination of Benefits
0174Nature of Service/Test/Observation
0175Master File Identifier Code
0177Confidentiality Code
0178File Level Event Code
0179Response Level
0180Masterfile Action Code
0181MFN Record-level Error Return
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
0260Patient Location Type
0261Location Equipment
0262Privacy Level
0263Level of Care
0265Specialty Type
0267Days of the Week
0269Charge On Indicator
0270Document Type
0271Document Completion Status
0272Document Confidentiality Status
0273Document Availability Status
0275Document Storage Status
0276Appointment reason codes
0277Appointment Type Codes
0278Filler status codes
0279Allow Substitution Codes
0280Referral Priority
0281Referral Type
0282Referral Disposition
0283Referral Status
0284Referral Category
0286Provider Role
0287Problem/Goal Action Code
0290MIME base64 encoding characters
0291Subtype of Referenced Data
0292Vaccines Administered
0294Time Selection Criteria Parameter Class Codes
0298CP Range Type
0301Universal ID Type
0305Person Location Type
0309Coverage Type
0311Job Status
0315Living Will Code
0316Organ Donor Code
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
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
0372Specimen Component
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
0398Continuation Style Code
0401Government Reimbursement Program
0402School Type
0403Language Ability
0404Language Proficiency
0406Participant Organization Unit Type
0409Application Change Type
0411Supplemental Service Information Values
0415Transfer Type
0416Procedure DRG Type
0417Tissue Type Code
0418Procedure Priority
0421Severity of Illness Code
0422Triage Code
0423Case Category Code
0424Gestation Category Code
0425Newborn Code
0426Blood Product Code
0427Risk Management Incident Code
0428Incident Type Code
0429Production Class Code
0430Mode of Arrival Code
0431Recreational Drug Use Code
0432Admission Level of Care Code
0433Precaution Code
0434Patient Condition Code
0435Advance Directive Code
0436Sensitivity to Causative Agent Code
0437Alert Device Code
0438Allergy Clinical Status
0440Data Types
0441Immunization Registry Status
0442Location Service Code
0443Provider Role
0444Name Assembly Order
0445Identity Reliability Code
0450Event Type
0455Type of Bill Code
0456Revenue code
0457Overall Claim Disposition Code
0459Reimbursement Action Code
0460Denial or Rejection Code
0465Name/Address Representation
0466Ambulatory Payment Classification Code
0468Payment Adjustment Code
0469Packaging Status Code
0470Reimbursement Type Code
0472TQ Conjunction ID
0473Formulary Status
0474Practitioner Organization Unit Type
0475Charge Type Reason
0477Controlled Substance Schedule
0478Formulary Status
0480Pharmacy Order Types
0482Order Type
0483Authorization Mode
0484Dispense Type
0485Extended Priority Codes
0487Specimen Type
0488Specimen Collection Method
0489Risk Codes
0490Specimen Reject Reason
0491Specimen Quality
0492Specimen Appropriateness
0493Specimen Condition
0494Specimen Child Role
0495Body Site Modifier
0496Consent Type
0497Consent Mode
0498Consent Status
0499Consent Bypass Reason
0500Consent Disclosure Level
0501Consent Non-Disclosure Reason
0502Non-Subject Consenter Reason
0503Sequence/Results Flag
0504Sequence Condition Code
0505Cyclic Entry/Exit Indicator
0506Service Request Relationship
0507Observation Result Handling
0508Blood Product Processing Requirements
0510Blood Product Dispense Status
0511BP Observation Status Codes Interpretation
0513Blood Product Transfusion/Disposition Status
0514Transfusion Adverse Reaction
0516Error Severity
0517Inform Person Code
0518Override Type
0520Message Waiting Priority
0523Computation Type
0524Sequence condition
0527Calendar Alignment
0528Event Related Period
0530Organization, Agency, Department
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
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
0909Patient Results Release Categorization Scheme
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