<status value="active"/> <experimental value="false"/> <date value="2026-03-17T21:02:03.8104715+00:00"/> <publisher value="FHIR Infrastructure"/> <contact> <name value="FHIR Infrastructure"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/fiwg"/> </telecom> </contact> <description value="This cross-version ValueSet represents content from `http://terminology.hl7.org/ValueSet/v3-SecurityIntegrityStatusObservationType|2.0.0` for use in FHIR R4."/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> <display value="World"/> </coding> </jurisdiction> <purpose value="This value set is part of the cross-version definitions generated to enable use of the value set `http://terminology.hl7.org/ValueSet/v3-SecurityIntegrityStatusObservationType|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-SecurityIntegrityStatusObservationType|2.0.0`, defined in FHIR R5 does not have any mapping to FHIR R4"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> <version value="8.0.0"/> <concept> <code value="SECINTSTOBS"/> <display value="security integrity status observation"/> </concept> </include> </compose> <expansion> <timestamp value="2026-03-17T21:02:03.8104715+00:00"/> <contains> <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/> <version value="8.0.0"/> <code value="SECINTSTOBS"/> <display value="security integrity status observation"/> </contains> </expansion> </ValueSet>

Generated Narrative: ValueSet R5-v3-SecurityIntegrityStatusObservationType-for-R4

This value set expansion contains 1 concepts.

System	Version	Code	Display	Definition
`http://terminology.hl7.org/CodeSystem/v3-ActCode`	8.0.0	SECINTSTOBS	security 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.