Consent Management

The Outcome Healthcare platform defaults to a model in which every patient in a geo-political area is considered a participant in the Health Information Exchange (HIE) by default.  However, the system can easily be configured to require that a patient “Opt In” in order for the patient’s data to be viewable.  When we receive messages that change a patient’s consent status (Opt-In or Opt-Out), the patient’s consent record is updated to reflect that.

As data is accessed by HIE participants, it can be filtered several ways:

  • Consent by patient, set at each participant
  • Sensitive Data as defined by standard / custom codes.  For example, mental health, STD / HIV, Part 2, etc.  (presently in design / development)
  • Exclude by source organization – allows participants receiving data to filter out data sources, such as:
    • Themselves
    • Organizations they are already exchanging data with
    • Organizations they do not wish to share data with
patient-data-consent

Centralized Consent Management for Patient Data

Outcome Healthcare offers a range of features for consent management, which include:

  • Granular Consent Levels: Patients can indicate their consent at various levels, including organization and HIE-wide
  • Consent Types: The system supports multiple opt in and opt out models
  • Historical Consent Records: The system maintains a history of all patient consent elections and authorizations, ensuring compliance with state statutes.
  • Consent Updates: The HIE can update patient consent through various methods, including the user interface (UI) and API call.  Privileged users can update consent through the Portal UI.
  • Auditing Capabilities: The system captures detailed audit logs related to consent management, including timestamps, consent types, and sources.
  • Outcome Healthcare’s platform includes “break the glass” functionality, to allow specific user roles to access Opt-Out or sensitive information.  This functionality is configurable and can be tailored to meet the needs of different organizations.

Consent is managed in our database and is utilized in the portal User Interface (UI), Data Query (DQ), Data Retrieval (DR) and Data Warehouse.  Our portal application allows users to view consent and for privileged users, set consent:

patient-data-set-consent

Consent Management – Active and Historical

Consent is utilized in the portal User Interface (UI), Data Query (DQ), Data Retrieval (DR) and Data Warehouse.

patient-data-consent