Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-SecurityDataIntegrityObservationValue-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5V3SecurityDataIntegrityObservationValueForR4 | ||
This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-SecurityDataIntegrityObservationValue|2.0.0 for use in FHIR R4.
This value set is part of the cross-version definitions generated to enable use of the
value set http://terminology.hl7.org/ValueSet/v3-SecurityDataIntegrityObservationValue|2.0.0 as defined in FHIR R5
in FHIR R4.
The source value set is bound to the following FHIR R5 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-SecurityDataIntegrityObservationValue|2.0.0, defined in FHIR R5 does not have any mapping to FHIR R4
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-ObservationValue version 📍2.1.0| Code | Display | Definition |
| CRYTOHASH | cryptographic hash function | Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit. *Rationale:* This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit. The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit. **Examples:** * SHA-1 * SHA-2 (Secure Hash Algorithm) |
| DIGSIG | digital signature | Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified. *Rationale:* This definition is intended to align with the ISO 22600-2 3.3.26 definition of digital signature: Data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient. |
This value set expansion contains 2 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/v3-ObservationValue | 2.1.0 | CRYTOHASH | cryptographic hash function | Security metadata observation value used to indicate the mechanism by which software systems can establish that data was not modified in transit. Rationale: This definition is intended to align with the ISO 22600-2 3.3.19 definition of cryptographic checkvalue: Information which is derived by performing a cryptographic transformation (see cryptography) on the data unit. The derivation of the checkvalue may be performed in one or more steps and is a result of a mathematical function of the key and a data unit. It is usually used to check the integrity of a data unit. Examples:
| ||
http://terminology.hl7.org/CodeSystem/v3-ObservationValue | 2.1.0 | DIGSIG | digital signature | Security metadata observation value used to indicate the mechanism by which software systems use digital signature to establish that data has not been modified. Rationale: This definition is intended to align with the ISO 22600-2 3.3.26 definition of digital signature: Data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g., by the recipient. |
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 |