United States Health Information Knowledgebase

 

HITSP CAP138 - Retrieve Pseudonym Version:1.0 25 January 2010


Type:Data Agreement
Start Date:2010-01-25
Scope:This Capability addresses interoperability requirements to support a particular type of anonymization that both removes the association with a data subject, and adds an association between a particular set of characteristics relating to the data subject and one or more pseudonyms. This enables a process of supplying an alternative identifier, which permits a patient to be referred to by a key that suppresses his/her actual identification information. The purpose of this Capability is to offer a pseudonymization framework for situations that require the use of specific data without disclosing the specific identity of patients or providers. Pseudo-identifiers are intended to allow accessibility to clinical information, while safeguarding any information that may compromise the privacy of the individual patient or provider. However, unlike anonymization, the alternative identifier key can be used to re-identify the individuals whose data was used.
Downloads
PDF
Download as a PDF file.
[Download PDF Reader Exit Disclaimer]
Download as an MS Excel™ spreadsheet.
[Download Excel Reader Exit Disclaimer]
Relationship Organization Item
is further defined by HITSP CAP 138 CONSTRAINTS AND ASSUMPTIONS   
is further defined by HITSP CAP 138 DESIGN SPECIFICATION   
is further defined by HITSP CAP 138 IMPLEMENTATION CONDITIONS   
is further defined by HITSP CAP 138 INFORMATION EXCHANGES   
is further defined by HITSP CAP 138 INTRODUCTION   
is further defined by HITSP CAP 138 REQUIREMENTS ANALYSIS   
is further defined by HITSP CAP 138 REQUIREMENTS MAPPED TO CONSTRUCTS   
is further defined by HITSP GUIDANCE FOR USE OF A CAPABILITY   

There are no Value Domains linked to HITSP CAP138 - Retrieve Pseudonym Version:1.0 25 January 2010.

HITSP Acronyms List
HITSP Data Architecture Technical Note TN903
HITSP TN 901 -Technical Note for Clinical Documents
HITSP TN904 Harmonization Framework and Exchange Architecture Technical Note
Security and Privacy Technical Note
Scroll To Top