Structured Data Capture, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/sdc/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/uv/sdc/ValueSet/dex-mimetype | Version: 3.0.0 | |||
Standards status: Draft | Maturity Level: 0 | Computable Name: DEXMappingLanguageMimeTypes | ||
Copyright/Legal: Mime types have no IP restrictions |
The list of mime types that identify mapping languages supported by DEX.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
urn:ietf:bcp:13
Code | Display |
application/sparql-results+xml | SPARQL |
application/sql | SQL |
application/xquery | X-Query |
This value set contains 3 concepts
Code | System | Display |
application/sparql-results+xml | urn:ietf:bcp:13 | SPARQL |
application/sql | urn:ietf:bcp:13 | SQL |
application/xquery | urn:ietf:bcp:13 | X-Query |
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 |