This page is part of the FHIR Specification v4.1.0: R4B Ballot. About the R4B version of FHIR. The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3
Clinical Genomics Work Group | Maturity Level: 1 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/repository-type |
Version: | 4.1.0 |
Name: | repositoryType |
Title: | repositoryType |
Definition: | Type for access of external URI. |
Committee: | Clinical Genomics Work Group |
OID: | 2.16.840.1.113883.4.642.3.230 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
http://hl7.org/fhir/repository-type
This expansion generated 11 Mar 2021
This value set contains 5 concepts
Expansion based on repositoryType v4.1.0 (CodeSystem)
All codes from system http://hl7.org/fhir/repository-type
Code | Display | Definition |
directlink | Click and see | When URL is clicked, the resource can be seen directly (by webpage or by download link format). |
openapi | The URL is the RESTful or other kind of API that can access to the result. | When the API method (e.g. [base_url]/[parameter]) related with the URL of the website is executed, the resource can be seen directly (usually in JSON or XML format). |
login | Result cannot be access unless an account is logged in | When logged into the website, the resource can be seen. |
oauth | Result need to be fetched with API and need LOGIN( or cookies are required when visiting the link of resource) | When logged in and follow the API in the website related with URL, the resource can be seen. |
other | Some other complicated or particular way to get resource from URL. | Some other complicated or particular way to get resource from URL. |
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 |