Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4-v3-CompressionAlgorithm-for-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Responsible: HL7 International / Terminology Infrastructure | Computable Name: R4V3CompressionAlgorithmForR5 | |
This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-CompressionAlgorithm|2018-08-12 for use in FHIR R5.
This value set is part of the cross-version definitions generated to enable use of the
value set http://terminology.hl7.org/ValueSet/v3-CompressionAlgorithm|2018-08-12 as defined in FHIR R4
in FHIR R5.
The source value set is bound to the following FHIR R4 elements:
Note that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://terminology.hl7.org/ValueSet/v3-CompressionAlgorithm|2018-08-12, defined in FHIR R4 does not have any mapping to FHIR R5
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm version 📍2018-08-12| Code | Display | Definition |
| BZ | bzip | bzip-2 compression format. See [http://www.bzip.org/] for more information. |
| DF | deflate | The deflate compressed data format as specified in RFC 1951 [http://www.ietf.org/rfc/rfc1951.txt]. |
| GZ | gzip | A compressed data format that is compatible with the widely used GZIP utility as specified in RFC 1952 [http://www.ietf.org/rfc/rfc1952.txt] (uses the deflate algorithm). |
| Z | compress | Original UNIX compress algorithm and file format using the LZC algorithm (a variant of LZW). Patent encumbered and less efficient than deflate. |
| Z7 | Z7 | 7z compression file format. See [http://www.7-zip.org/7z.html] for more information. |
| ZL | zlib | A compressed data format that also uses the deflate algorithm. Specified as RFC 1950 [http://www.ietf.org/rfc/rfc1952.txt] |
This value set expansion contains 6 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm | 2018-08-12 | BZ | bzip | bzip-2 compression format. See [http://www.bzip.org/] for more information. | ||
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm | 2018-08-12 | DF | deflate | The deflate compressed data format as specified in RFC 1951 [http://www.ietf.org/rfc/rfc1951.txt]. | ||
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm | 2018-08-12 | GZ | gzip | A compressed data format that is compatible with the widely used GZIP utility as specified in RFC 1952 [http://www.ietf.org/rfc/rfc1952.txt] (uses the deflate algorithm). | ||
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm | 2018-08-12 | Z | compress | Original UNIX compress algorithm and file format using the LZC algorithm (a variant of LZW). Patent encumbered and less efficient than deflate. | ||
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm | 2018-08-12 | Z7 | Z7 | 7z compression file format. See [http://www.7-zip.org/7z.html] for more information. | ||
http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm | 2018-08-12 | ZL | zlib | A compressed data format that also uses the deflate algorithm. Specified as RFC 1950 [http://www.ietf.org/rfc/rfc1952.txt] |
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 |