Customer database management is quite crucial
in the present age. Companies are maintaining personal records of their
customers to utilize this kind of information in the product development and
service improvement processes. Customer details and frequency of purchases
enable the company to forecast future demand. While other than this, some organizations
are storing customer data for other purposes such as for the security and
benefit of customers. For instance, in healthcare centers and hospitals medical
staff store healthcare records and treatment details of the patients stored in
their records that benefit a patient to get better treatment for the next time
as whenever that patient visits a hospital doctors quickly understands his/her medical
history and suggest a better treatment for his/her problem.
Somehow, keeping personal data of customers
stored in the databases is not fully safe. To avoid issues database managers
sometimes follow up redaction policy for electronic health records. Name can
direct us as to our required customer data details but some organizations
redact name and address of customers because of security reasons. In some
healthcare centers, the customer (patient) details are stored with the use of
the fake name. Healthcare records management redact name, address, social
security number, and date of birth of the customers because of the security
issues. However, reeducation of such important information can cause ambiguity
and confusion sometimes. At the same time searching data records with the name
can lead to a list of customers or patients with the same name (Sutter, 2016).
According to the Oracle learning library
video, speaker searched for the records of a person by using his name and he
found more than one matches. More than one matches put him in the state of
confusion as he was not sure which his required one was. If we take this
situation in the real databases of healthcare centers we can say that searching
customer data records by names are not simple unless the name is unique.
Furthermore, the healthcare systems address is not an essential detail for medical
support (Library, 2014). The address is
unnecessary information which should be redacted from the databases. In the presence of various issues related to finding
patient or customer medical records through the use of fingerprint is quite
easy and reliable. Redaction is not necessary to anonymize an electronic health
record. Redaction just makes it possible for the database management to easily
get understanding about the required details and information of a customer
which relates to the healthcare system or medical records.
Furthermore, redaction also provides security
to the personal data of customers. Fingerprints based data stored in the
healthcare databases will enable the database management to easily provide an
actual result from all stored data as fingerprints of all human being are
different from each other. Thus storing medical records with finders is a quite
easy and reliable way to get information about user or customer. Excluding the
ease of access and accuracy, another benefit of fingerprint-based data is that
because of this security issues will decrease as hackers would not be able to
use this data by identifying the customer (Emam, 2011).
References of Healthcare
Emam, K. E.
(2011). Methods for the de-identification of electronic health records for
genomic research. Genome Med., 3(4).
Library,
O. L. (2014). Data Redaction Demo for Oracle Advanced Security (Oracle
Database 12c) - Part 2. Retrieved from www.youtube.com:
https://www.youtube.com/watch?v=sWjic4xMHbM
Sutter,
p. B. (2016). 11 - Demonstration of Data Obfuscation Techniques.
Retrieved from www.youtube.com: https://www.youtube.com/watch?v=VDVhWro8to0