Communication Step Summary

Description:

This EHR Communication Step will use client and provider identifying information to request a patient’s masked health information, to be returned as visible data for display by the POS system.

The information types of a patient’s Personal Health Information to be unmasked may be clinical values contained in different records such as:

• Demographic Information
• Clinical Event
• Lab Results
• etc

When this request is processed by the EHRi system, it is responsible for:

• Logging who authorized this consent override
• Logging the patient identifier
• Logging the source application id
• Logging the location id of the request
• Logging what information was requested to be unmasked
• Logging the date / time of the request
• Logging the reason why the data should be unmaske

Used by:

Uses: IIP_Get

Communication Structure:

This EHR Communication Step is composed of the following generic transaction component wrappers that encapsulate and provide the context for the HL7 v3 message payload.

HL7 Trigger:

·User requested query

Communication Step Type:

·Get

Domain:

-EHR

-Lab

-Drug

-DI

-Public Health

Constraint:

-Unmask Directives

Message:

Inputs:

• Header
  • EHRi Interface Identifiers
• Payload
  • Privacy, Security, Consent view (constrained for Unmask Directives)
    • Unmask Information ID (Instance IDs of entities / attributes to be unmasked)
    • Unmask Information Type Description
    • Unmask Request Authorized User ID
    • Unmask Request Date / Time
    • Unmask Reason

Rationale

This Communication Step allows a health care provider, who has a patient’s consent, to review a patient’s information unmasked.