FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r4b
Resource TypeValueSet
IdValueSet-R5-v3-SecurityIntegrityObservationType-for-R4B.json
FHIR VersionR4B
Sourcehttp://hl7.org/fhir/uv/xver-r5.r4b/0.0.1-snapshot-2/ValueSet-R5-v3-SecurityIntegrityObservationType-for-R4B.html
URLhttp://hl7.org/fhir/5.0/ValueSet/R5-v3-SecurityIntegrityObservationType-for-R4B
Version0.0.1-snapshot-2
Statusactive
Date2025-09-01T22:37:05.396272+10:00
NameR5_v3_SecurityIntegrityObservationType_for_R4B
TitleCross-version VS for R5.SecurityIntegrityObservationType for use in FHIR R4B
Realmuv
Authorityhl7
DescriptionThis cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-SecurityIntegrityObservationType|2.0.0 for use in FHIR R4B. Concepts not present here have direct `equivalent` mappings crossing all versions from R5 to R4B.

Resources that use this resource

No resources found


Resources that this resource uses

CodeSystem
v3-ActCodeActCode

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet R5-v3-SecurityIntegrityObservationType-for-R4B

This value set expansion contains 7 concepts.

CodeSystemDisplayDefinition
  SECINTOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity integrity observation

Type of security metadata observation made about the integrity of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.

Rationale: A security integrity observation supports the requirement to guard against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity. (44 U.S.C., SEC. 3542)

Examples: Types of security integrity metadata include:

  • Integrity status, which indicates the completeness or workflow status of an IT resource (data, information object, service, or system capability)
  • Integrity confidence, which indicates the reliability and trustworthiness of an IT resource
  • Integrity control, which indicates pertinent handling caveats, obligations, refrain policies, and purpose of use for the resource
  • Data integrity, which indicate the security mechanisms used to ensure that the accuracy and consistency are preserved regardless of changes made (ISO/IEC DIS 2382-8)
  • Alteration integrity, which indicate the security mechanisms used for authorized transformations of the resource
  • Integrity provenance, which indicates the entity responsible for a report or assertion relayed "second-hand" about an IT resource
  SECALTINTOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity alteration integrity observation

Type of security metadata observation made about the alteration integrity of an IT resource (data, information object, service, or system capability), which indicates the mechanism used for authorized transformations of the resource.

Examples: Types of security alteration integrity observation metadata, which may value the observation with a code used to indicate the mechanism used for authorized transformation of an IT resource, including:

  • translation
  • syntactic transformation
  • semantic mapping
  • redaction
  • masking
  • pseudonymization
  • anonymization
  SECDATINTOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity data integrity observation

Type of security metadata observation made about the data integrity of an IT resource (data, information object, service, or system capability), which indicates the security mechanism used to preserve resource accuracy and consistency. Data integrity is defined by ISO 22600-23.3.21 as: "The property that data has not been altered or destroyed in an unauthorized manner", and by ISO/IEC 2382-8: The property of data whose accuracy and consistency are preserved regardless of changes made."

Examples: Types of security data integrity observation metadata, which may value the observation, include cryptographic hash function and digital signature.

  SECINTCONOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity integrity confidence observation

Type of security metadata observation made about the integrity confidence of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions.

Examples: Types of security integrity confidence observation metadata, which may value the observation, include highly reliable, uncertain reliability, and not reliable.

Usage Note: A security integrity confidence observation on an Act may indicate that a valued Act.uncertaintycode attribute has been overridden by the entity responsible for ascribing the SecurityIntegrityConfidenceObservationValue. This supports the business requirements for increasing or decreasing the assessment of the reliability or trustworthiness of an IT resource based on parameters beyond the original assignment of an Act statement level of uncertainty.

  SECINTPRVABOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity integrity provenance asserted by observation

Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that made assertions about the resource. The asserting entity may not be the original informant about the resource.

Examples: Types of security integrity provenance asserted by observation metadata, which may value the observation, including:

  • assertions about an IT resource by a patient
  • assertions about an IT resource by a clinician
  • assertions about an IT resource by a device
  SECINTPRVRBOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity integrity provenance reported by observation

Type of security metadata observation made about the integrity provenance of an IT resource (data, information object, service, or system capability), which indicates the entity that reported the existence of the resource. The reporting entity may not be the original author of the resource.

Examples: Types of security integrity provenance reported by observation metadata, which may value the observation, include:

  • reports about an IT resource by a patient
  • reports about an IT resource by a clinician
  • reports about an IT resource by a device
  SECINTSTOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity integrity status observation

Type of security metadata observation made about the integrity status of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Indicates the completeness of an IT resource in terms of workflow status, which may impact users that are authorized to access and use the resource.

Examples: Types of security integrity status observation metadata, which may value the observation, include codes from the HL7 DocumentCompletion code system such as legally authenticated, in progress, and incomplete.


Source1

{
  "resourceType": "ValueSet",
  "id": "R5-v3-SecurityIntegrityObservationType-for-R4B",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "extension": [
        {
          "url": "packageId",
          "valueId": "hl7.fhir.uv.xver-r5.r4b"
        },
        {
          "url": "version",
          "valueString": "0.0.1-snapshot-2"
        }
      ],
      "url": "http://hl7.org/fhir/StructureDefinition/package-source"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/5.0/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/5.0/ImplementationGuide/hl7.fhir.uv.xver-r5.r4b"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/5.0/ValueSet/R5-v3-SecurityIntegrityObservationType-for-R4B",
  "version": "0.0.1-snapshot-2",
  "name": "R5_v3_SecurityIntegrityObservationType_for_R4B",
  "title": "Cross-version VS for R5.SecurityIntegrityObservationType for use in FHIR R4B",
  "status": "active",
  "experimental": false,
  "date": "2025-09-01T22:37:05.396272+10:00",
  "publisher": "FHIR Infrastructure",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-SecurityIntegrityObservationType|2.0.0 for use in FHIR R4B. Concepts not present here have direct `equivalent` mappings crossing all versions from R5 to R4B.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "compose": {
    "include": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "concept": [
          {
            "code": "SECINTOBS",
            "display": "security integrity observation"
          },
          {
            "code": "SECALTINTOBS",
            "display": "security alteration integrity observation"
          },
          {
            "code": "SECDATINTOBS",
            "display": "security data integrity observation"
          },
          {
            "code": "SECINTCONOBS",
            "display": "security integrity confidence observation"
          },
          {
            "code": "SECINTPRVABOBS",
            "display": "security integrity provenance asserted by observation"
          },
          {
            "code": "SECINTPRVRBOBS",
            "display": "security integrity provenance reported by observation"
          },
          {
            "code": "SECINTSTOBS",
            "display": "security integrity status observation"
          }
        ]
      }
    ]
  },
  "expansion": {
    "timestamp": "2025-09-01T22:37:05.396272+10:00",
    "contains": [
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECINTOBS",
        "display": "security integrity observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECALTINTOBS",
        "display": "security alteration integrity observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECDATINTOBS",
        "display": "security data integrity observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECINTCONOBS",
        "display": "security integrity confidence observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECINTPRVABOBS",
        "display": "security integrity provenance asserted by observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECINTPRVRBOBS",
        "display": "security integrity provenance reported by observation"
      },
      {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "version": "8.0.0",
        "code": "SECINTSTOBS",
        "display": "security integrity status observation"
      }
    ]
  }
}