Skip to content
Puede usar nuestro buscador para encontrar información sobre los productos y soluciones de InterSystems, las oportunidades de desarrollo profesional, los casos de uso, novedades y mucho más.

Advisory: When No Consent Group is Specified, Clinical Consent Rules May Fail

March 1, 2022 – Advisory: When No Consent Group is Specified, Clinical Consent Rules May Fail

InterSystems has identified a defect affecting Clinical Information Type (CIT) consent. In certain situations, if no consent group is specified, the CIT consent rules are ignored, and the user experiences the opposite of what was intended.

This issue affects all versions of HealthShare Information Exchange and Unified Care Record through version 2021.2.

Clinical Information Type (CIT) consent may be configured with a decision to show or block data for all users except those who are in the consent groups specified in the policy. These decisions are effective when one or more consent groups are specified. However, the policies are not effective if no consent group is specified. In these situations, the rules are ignored, and the opposite behavior is experienced: the blocking rule will permit data to be displayed to all users and the show rule will block the data from all users.

The affected consent decisions are as follows:

  • System-Wide Policy:
    • Always Block Except
    • Always Show Except
    • Default Block Except
    • Default Show Except
  • Facility-Wide Policy:
    • Always Block Except
    • Always Show Except
    • Default Block Except
    • Default Show Except
  • Patient Policy:
    • Block Except
    • Show Except

This issue has been rated as a Low Risk due to the fact that these policies are intended to be used with one or more specified consent groups and omitting a group is most likely a configuration mistake and would be detected during testing.
The following decisions should be used when consent groups are not relevant:

  • System-Wide Policy:
    • Always Block
    • Always Show
    • Default Block
    • Default Show
  • Facility-Wide Policy:
    • Always Block
    • Always Show
    • Default Block
    • Default Show
  • Patient Policy:
    • Block
    • Show

InterSystems recommends that customers review their consent policies to ensure that any Block Except and Show Except consent policies have one or more consent groups specified. If that is not the case, customers should add one or more consent groups or use a more appropriate decision option as described above.
This defect is identified as HSIEC-4741 and will be addressed in a future version.

RELATED TOPICS

Latest Alerts & Advisories

Aug 15 2024
InterSystems has corrected a defect that can cause database corruption or errors with multi-volume databases under extremely rare circumstances. Only databases that have been truncated are at risk.
Jul 24 2024
There are four alerts in the HS2024-03 Alert Communication. A summary of each alert is shown below. Details for each alert are contained in the linked document.
Jun 24 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
May 30 2024
Beginning with the release of InterSystems IRIS® data platform 2022.3, InterSystems corrected the license enforcement mechanism to include REST and SOAP requests. Due to this change, environments with non-core-based licenses that use REST or SOAP may experience greater license utilization after upgrading. To determine if this advisory applies to your InterSystems license, follow the instructions in the FAQ linked below.
May 01 2024
InterSystems has corrected an issue that can cause a small number of SQL queries to return incorrect results. See below for the specifics on impacted queries.
Apr 08 2024
InterSystems has encountered a defect that causes some upgrades of HealthShare® Health Connect to fail. This only affects instances that are not licensed for the use of FHIR® and that have interoperability-enabled namespaces. Under these conditions, the upgrade fails with an error.
Mar 19 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
Feb 27 2024
There is 1 alert in the HealthShare HS2024-limited Alert communication. An alert summary for the issue is shown is in the table below. Details for the alert are contained in the attached document: HS2024 Limited Communication.
Feb 01 2024
There are 2 alerts in the HealthShare HS2024-02 Alert communication. An alert summary for each issue is shown is in the table below. Details for each alert are contained in the attached document: HS2024-02-Communication.