API for the Exchange of Medicinal Product Information (APIX)
0.1.0 - ci-build
API for the Exchange of Medicinal Product Information (APIX), published by Gravitate Health Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/cander2/apix-ig/ and changes regularly. See the Directory of published versions
Official URL: http://example.com/fhir/ValueSet/apix-submission-type | Version: 0.1.0 | |||
Draft as of 2025-07-06 | Computable Name: ApixSubmissionTypeValueSet |
Codes for types of regulatory submissions.
References
http://example.com/fhir/CodeSystem/apix-submission-type
Code | Display |
variation | Variation |
initial | Initial Application |
renewal | Renewal |
Expansion performed internally based on codesystem APIX Submission Type Code System v0.1.0 (CodeSystem)
This value set contains 3 concepts
Code | System | Display (en-US) |
variation | http://example.com/fhir/CodeSystem/apix-submission-type | Variation |
initial | http://example.com/fhir/CodeSystem/apix-submission-type | Initial Application |
renewal | http://example.com/fhir/CodeSystem/apix-submission-type | Renewal |
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 |