Knowledge Base for Investigators

Searching for patient related article? Navigate to the 
Knowledge Base for Patients

PII Architecture

Overview

inCytes™ captures personally identifiable information “PII” from two types of licensees: the Subscriber and their patients. The types of PII captured, the purpose of capture, and the role of inCytes™ as Data Controller or Data Processor are different for both licensee groups. These differences are identified and consented to within our License Agreement.

This document concerns the technical processes, shared among both Licensee Groups, for how we receive, pseudonymize, encrypt, store and then recombine PII with health data for authenticated users only. This solution takes advantage of our licensed sub-processor Amazon Web Services “AWS” which employs a microservice AWS Cognito.

User Registration  

  • User registers on inCytes™ platform enters select PII.
  • All data is transferred over a secured, encrypted HTTPS to Amazon AWS secure perimeter.
  • inCytes Backend API processes data on Amazon EC2 instance.
  • inCytes Backend API extracts PII, defined as first name, last name, email, password, phone number, and transmits over secure HTTPS to AWS Cognito Services.
  • AWS Cognito generates an alphanumeric Subject ID, and stores the PII in the region of controller’s choice: Canada or US, and transmits back only the Subject ID.
  • inCytes Backend API saves the Subject ID alongside non-PII data to an Amazon RDS instance.

Authenticated User Login  

  • The user enters their username, password, if required, completes Recaptcha to authenticate human request.
  • Username and password are transmitted over a secured, encrypted HTTPS to Amazon AWS secure perimeter.
  • inCytes Backend API transmits username and password to AWS Cognito Services to authenticate the Subscriber.
  • Upon successful authentication, AWS Cognito Service returns Subject ID, Authentication Token and Refresh Token.
  • User-provided access to Amazon RDS, with permissions, role, and other data defined by Cognito Subject ID.

Authenticated User PII Access

  • Authenticated User requests data from RDS Instance
  • If they have no PII access, they are presented with Non-PII and Subject IDs
  • If they have PII access, Subject IDs are transmitted to AWS Cognito.
  • AWS Cognito authenticates Subject IDs and User Access and returns PII
  • PII and Non-PII made temporarily available for authenticated user accounts until sign out.

Search keywords:

Haven't found a solution?

CONTACT US