ValueSet Comparison between http://terminology.hl7.org/ValueSet/v2-0719 vs http://terminology.hl7.org/ValueSet/v2-0719

Messages

ErrorValueSet.versionValues for version differ: '2.0.0' vs '3.0.0'
InformationValueSet.statusValues for status differ: 'active' vs 'retired'
ErrorValueSetError Expanding left:Error from server: Unable to provide support for code system http://terminology.hl7.org/CodeSystem/v3-ActCode version 2.139.0 (known versions = 7.0.0)
ErrorValueSetError Expanding right:Error from server: Unable to provide support for code system http://terminology.hl7.org/CodeSystem/v3-ActCode version 2.139.0 (known versions = 7.0.0)

Metadata

NameValueComments
.compose.inactive
    .compose.lockedDate
      .copyrightCopyright HL7. Licensed under creative commons public domain
        .date2019-12-01
          .descriptionValue Set of codes that specify the reason for the restricted access. Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an "employee" sensitivity code would make little sense for use outside of a policy domain. "Taboo" would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.titleValue Set of codes that specify the reason for the restricted access.Value Set of codes that specify the reason for the restricted access. Sensitivity codes are not useful for interoperability outside of a policy domain because sensitivity policies are typically localized and vary drastically across policy domains even for the same information category because of differing organizational business rules, security policies, and jurisdictional requirements. For example, an "employee" sensitivity code would make little sense for use outside of a policy domain. "Taboo" would rarely be useful outside of a policy domain unless there are jurisdictional requirements requiring that a provider disclose sensitive information to a patient directly. Sensitivity codes may be more appropriate in a legacy system's Master Files in order to notify those who access a patient's orders and observations about the sensitivity policies that apply. Newer systems may have a security engine that uses a sensitivity policy's criteria directly. The specializable Sensitivity Act.code may be useful in some scenarious if used in combination with a sensitivity identifier and/or Act.titleValue Set of codes that specify the reason for the restricted access. Note that this resource was created in THO in error due to an oversight in the import processing.
          • Values Differ
          .experimentalfalse
            .immutable
              .jurisdiction
                .nameInformationSensitivityPolicy
                  .publisherHL7, Inc
                    .purpose
                      .statusactiveretired
                      • Values Differ
                      .titleInformationSensitivityPolicy
                        .urlhttp://terminology.hl7.org/ValueSet/v2-0719
                          .version2.0.03.0.0
                          • Values Differ

                          Definition

                          ItemPropertyValueComments
                          .includehttp://terminology.hl7.org/CodeSystem/v3-ActCode2.139.0

                            Expansion

                            Unable to generate expansion - see errors