Electronic Medicinal Product Information (ePI) FHIR Implementation Guide, published by HL7 International - Biomedical Research & Regulation Work Group. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/emedicinal-product-info/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/uv/emedicinal-product-info/ValueSet/epiType | Version: 1.0.0 | |||
Active as of 2024-07-15 | Computable Name: VsEpiType | |||
Copyright/Legal: This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc |
ePI document types
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet epiType
http://loinc.org
Code | Display |
34390-5 | HUMAN OTC DRUG LABEL |
34391-3 | HUMAN PRESCRIPTION DRUG LABEL |
Generated Narrative: ValueSet
Expansion based on Loinc v2.77
This value set contains 2 concepts
Code | System | Display |
34390-5 | http://loinc.org | FDA product label Human OTC drug label |
34391-3 | http://loinc.org | FDA product label Human prescription drug label |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |