Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

ValueSet: R5V3SecurityTrustObservationTypeForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-v3-SecurityTrustObservationType-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5V3SecurityTrustObservationTypeForR4

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/v3-SecurityTrustObservationType|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-SecurityTrustObservationType|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-SecurityTrustObservationType|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)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActCode version 📍8.0.0
    CodeDisplayDefinition
    SECTRSTOBSSECTRSTOBSAn observation identifying trust metadata about an IT resource (data, information object, service, or system capability), which may be used as a trust attribute to populate a computable trust policy, trust credential, trust assertion, or trust label field in a security label or trust policy, which are principally used for authentication, authorization, and access control decisions.
    TRSTACCRDOBStrust accreditation observationType of security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework.
    TRSTAGREOBStrust agreement observationType of security metadata observation made about privacy and security requirements with which a security domain must comply. \[ISO IEC 10181-1\]
    TRSTCERTOBStrust certificate observationType of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). \[Based on ISO IEC 10181-1\]

    **For example,**

    * A Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. For example, a particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. \[Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.
    * A Certificate Practice Statement (CSP), which is a statement of the practices which an Authority employs in issuing and managing certificates. \[Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.\]
    TRSTFWKOBStrust framework observationType of security metadata observation made about a complete set of contracts, regulations or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. \[Kantara Initiative\]
    TRSTLOAOBStrust assurance observationType of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.
    TRSTMECOBStrust mechanism observationType of security metadata observation made about a security architecture system component that supports enforcement of security policies.

 

Expansion

This value set expansion contains 7 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  SECTRSTOBSSECTRSTOBS

An observation identifying trust metadata about an IT resource (data, information object, service, or system capability), which may be used as a trust attribute to populate a computable trust policy, trust credential, trust assertion, or trust label field in a security label or trust policy, which are principally used for authentication, authorization, and access control decisions.

http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  TRSTACCRDOBStrust accreditation observation

Type of security metadata observation made about the formal declaration by an authority or neutral third party that validates the technical, security, trust, and business practice conformance of Trust Agents to facilitate security, interoperability, and trust among participants within a security domain or trust framework.

http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  TRSTAGREOBStrust agreement observation

Type of security metadata observation made about privacy and security requirements with which a security domain must comply. [ISO IEC 10181-1]

http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  TRSTCERTOBStrust certificate observation

Type of security metadata observation made about a set of security-relevant data issued by a security authority or trusted third party, together with security information which is used to provide the integrity and data origin authentication services for an IT resource (data, information object, service, or system capability). [Based on ISO IEC 10181-1]

For example,

  • A Certificate Policy (CP), which is a named set of rules that indicates the applicability of a certificate to a particular community and/or class of application with common security requirements. For example, a particular Certificate Policy might indicate the applicability of a type of certificate to the authentication of electronic data interchange transactions for the trading of goods within a given price range. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.
  • A Certificate Practice Statement (CSP), which is a statement of the practices which an Authority employs in issuing and managing certificates. [Trust Service Principles and Criteria for Certification Authorities Version 2.0 March 2011 Copyright 2011 by Canadian Institute of Chartered Accountants.]
http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  TRSTFWKOBStrust framework observation

Type of security metadata observation made about a complete set of contracts, regulations or commitments that enable participating actors to rely on certain assertions by other actors to fulfill their information security requirements. [Kantara Initiative]

http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  TRSTLOAOBStrust assurance observation

Type of security metadata observation made about the digital quality or reliability of a trust assertion, activity, capability, information exchange, mechanism, process, or protocol.

http://terminology.hl7.org/CodeSystem/v3-ActCode8.0.0  TRSTMECOBStrust mechanism observation

Type of security metadata observation made about a security architecture system component that supports enforcement of security policies.


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