Our 3PSecure™ Solution
Data Owner
ie: Traditional or
Virtual Care Provider
3PSecure™
Secure Token Vault
& Token Engine
TOKENIZE
REDACT
MASK
AI/BI Analytics
or Laboratory Analysis
or Second Opinion Provider
3PSecure™
Secure Token Vault
& Token Engine
DETOKENIZE
Data Owner
ie: Traditional or
Virtual Care Provider
ACTIONABLE INSIGHTS
or LAB RESULTS or SECOND OPINION
appended to record
DEFINING the Problem:
During the course of a clinical or virtual care visit, providers append a patient's medical record (which contains PHI) with current clinical data. HIPAA requires that all PHI must be secured. The 21st Century Cures Act mandates that all information be shareable.
REDEFINING the Possible:
There is no value to fraudsters because PHI is tokenized, redacted & masked.
TOKENIZE:
◼︎ Record Number
◼︎ Patient Name
◼︎ Patient ID Number
◼︎ Insurance ID Number
When you TOKENIZE DATA:
◼︎ Personally identifiable information is stripped from record
◼︎ PHI is substituted with alphanumeric token
◼︎ May only be detokenized by genuine data owner
◼︎ Holds no monetizable value for fraudsters
REDACT:
◼︎ Social Security Number
◼︎ City of residence
◼︎ State of residence
When you REDACT DATA:
◼︎ Redacted data serves no purpose to analysis
◼︎ Redacted data poses a level of security risk if transmitted in the clear
◼︎ Redacted data is deleted from the record
MASK:
◼︎ Only LAST TWO digits of zipcode
◼︎ Day/Month of Birth but NOT year
When you MASK DATA:
◼︎ Data is partially redacted to protect patient privacy
◼︎ Data that remains unmasked reveals health conditions related to age, environment, and other factors
POSSIBLE: Secure your PHI anywhere in the ecosystem.
Data Owner
3PSecure Engine
SECURE ENVIRONMENT
Ecosystem
ENRICHED RECORD
with Secure PHI
MEDICAL RECORD
with Secure PHI
MEDICAL RECORD
with Unsecured PHI
ENRICHED RECORD
with Detokenized PHI
Provider appends patient record (which contains PHI) with current clinical data.
Medical record is ingested by
3PSecure and stripped of sensitive PHI.
Data is tokenized, redacted & masked before being shared with third parties.
Secure records may undergo AI/BI analysis or be reviewed for second opinion.
Enriched and/or appended record returns to 3PSecure Engine for PHI detokenization.
3PSecure detokenizes PHI in original record while retaining enriched & appended data.
Detokenized & enriched record is returned to data owner. PHI was never exposed.
Analytic insights or other enrichment can be applied at patient level for better outcomes.