Skip to main content

Description: The default behaviour of Global Search promotes the disclosure of Personal Health Information.

 

Scenario:

- Alice and Bob are Health Care co-workers at the Acme Health Care Organization.

- Acme uses Health Cloud to manage patient care.

- Alice and Bob are both clinical users of the Acme Health Cloud solution.

- Bob is also a patient of Acme Health Care, with clinical records in the Health Cloud Solution.

- Alice is not actively involved with Bob’s care, but is not restricted from accessing Bob’s patient records under certain scenarios, such as on-call or emergency situations.

- Bob’s patient status should not be revealed to Alice through incidental disclosure in the user interface while searching for Bob’s provider account.

 

Under its current configuration, when Alice searches for Bob the Provider, Global Search will incidentally reveal to Alice that Bob is a Patient. *

 

(Person Accounts are used for Patient record type and Provider record type, see @Tina Woodall's explanation of this approach here https://youtu.be/44VRFIFZepA?t=794)

 

For our implementation, there is no Use Case for enabling Global Search. In the scenario above, the Global Search feature becomes a liability.

 

Alternate search capability within the application will return search results that will be constrained by context. We will have separate Patient Search, Provider Search and Facility Search pages. **

 

In other words, a user will search exclusively for a provider or patient, but never for both at the same time, as this can lead to a breach. This model also assists with logging/auditing, for tracking suspicious behavior.

 

In short, a mechanism is required to disable/suppress/hide the Global Search box in the Health Cloud User Interface, because

  • A) there is no Use Case that requires this feature
  • B) it is a navigation feature that bypasses structured workflow(hindering training/usability)
  • C) its presence becomes a privacy liability.

 

* Scoping Rules were discussed as a mitigation with the Salesforce solution team, but this approach is problematic due to the side effects of the Scoping Rules in other parts of the application.

** Account Lookup filters are workable in the context specific search pages. (Patient / Provider)

4 Antworten
  1. 4. Aug. 2022, 04:41

    Not the answer a tech person likes to hear, but our legal teams insisted upon separate Salesforce orgs to prevent the exposure of PHI for this reason. 

     

    I think you can get to a safe place with Salesforce security inside of a single org but you can't provide a guarantee that PHI won't be exposed at some level to someone who is not supposed to have it -- the worst case being someone who is not a covered entity under HIPAA.