This page is part of the FHIR Specification v6.0.0-ballot3: Release 6 Ballot (3rd Draft) (see Ballot Notes). The current version is 5.0.0.  For a full list of available versions, see the Directory of published versions 
| Biomedical Research and Regulation  Work Group | Maturity Level: 1 | Trial Use | Use Context: Country: World | 
| Official URL: http://hl7.org/fhir/ValueSet/interaction-type | Version: 6.0.0-ballot3 | |||
| draft as of 2020-12-28 | Computable Name: InteractionType | |||
| Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.3115 | |||
This value set is used in the following places:
A categorisation for an interaction between two substances.
Generated Narrative: ValueSet interaction-type
Last updated: 2025-04-01T12:16:37.966+11:00
Profile: Shareable ValueSet
http://hl7.org/fhir/interaction-type
This expansion generated 01 Apr 2025
ValueSet
Expansion performed internally based on codesystem Interaction Type v6.0.0-ballot3 (CodeSystem)
This value set contains 4 concepts
| Code | System | Display | 
| drug-drug | http://hl7.org/fhir/interaction-type | drug to drug interaction | 
| drug-food | http://hl7.org/fhir/interaction-type | drug to food interaction | 
| drug-test | http://hl7.org/fhir/interaction-type | drug to laboratory test interaction | 
| other | http://hl7.org/fhir/interaction-type | other interaction | 
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
| Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information | 
| Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) | 
| Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') | 
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application | 
| Definition | An explanation of the meaning of the concept | 
| Comments | Additional notes about how to use the code |