Consumer Health Informatics, Mobile Health, and Social Media for Health: Part...
Health Information Privacy and Security (March 30, 2016)
1. Health Information
Privacy & Security
Nawanan Theera-Ampornpunt, M.D., Ph.D.
Faculty of Medicine Ramathibodi Hospital
Mahidol University
For the Faculty of Pharmacy, Silpakorn University
March 19, 2016
http://www.SlideShare.net/Nawanan
2. Introduction to Information Privacy & Security
Protecting Information Privacy & Security
User Security
Software Security
Cryptography
Malware
Security Standards
Privacy & Security Laws
Outline
10. Sources of the Threats
Hackers
Viruses & Malware
Poorly-designed systems
Insiders (Employees)
People’s ignorance & lack of knowledge
Disasters & other incidents affecting
information systems
11. Information risks
Unauthorized access & disclosure of confidential information
Unauthorized addition, deletion, or modification of information
Operational risks
System not functional (Denial of Service - DoS)
System wrongly operated
Personal risks
Identity thefts
Financial losses
Disclosure of information that may affect employment or other
personal aspects (e.g. health information)
Physical/psychological harms
Organizational risks
Financial losses
Damage to reputation & trust
Etc.
Consequences of Security Attacks
13. Privacy: “The ability of an individual or group
to seclude themselves or information about
themselves and thereby reveal themselves
selectively.” (Wikipedia)
Security: “The degree of protection to safeguard
... person against danger, damage, loss, and
crime.” (Wikipedia)
Information Security: “Protecting information
and information systems from unauthorized
access, use, disclosure, disruption, modification,
perusal, inspection, recording or destruction”
(Wikipedia)
Privacy & Security
16. Examples of Integrity Risks
http://www.wired.com/threatlevel/2010/03/source-code-hacks/
http://en.wikipedia.org/wiki/Operation_Aurora
“Operation Aurora”
Alleged Targets: Google, Adobe, Juniper Networks,
Yahoo!, Symantec, Northrop Grumman, Morgan Stanley,
Dow Chemical
Goal: To gain access to and potentially modify source
code repositories at high tech, security & defense
contractor companies
17. Examples of Integrity Risks
http://news.softpedia.com/news/700-000-InMotion-Websites-Hacked-by-TiGER-M-TE-223607.shtml
Web Defacements
18. Examples of Availability Risks
http://en.wikipedia.org/wiki/Blaster_worm
Viruses/worms that led to instability &
system restart (e.g. Blaster worm)
19. Examples of Availability Risks
http://en.wikipedia.org/wiki/Ariane_5_Flight_501
Ariane 5 Flight 501 Rocket Launch Failure
Cause: Software bug on rocket acceleration due to data conversion
from a 64-bit floating point number to a 16-bit signed integer without
proper checks, leading to arithmatic overflow
23. Attack
An attempt to breach system security
Threat
A scenario that can harm a system
Vulnerability
The “hole” that is used in the attack
Common Security Terms
24. Identify some possible means an
attacker could use to conduct a
security attack
Class Exercise
26. Alice
Simplified Attack Scenarios
Server Bob
- Physical access to client computer
- Electronic access (password)
- Tricking user into doing something
(malware, phishing & social
engineering)
Eve/Mallory
27. Alice
Simplified Attack Scenarios
Server Bob
- Intercepting (eavesdropping or
“sniffing”) data in transit
- Modifying data (“Man-in-the-
middle” attacks)
- “Replay” attacks
Eve/Mallory
28. Alice
Simplified Attack Scenarios
Server Bob
- Unauthorized access to servers through
- Physical means
- User accounts & privileges
- Attacks through software vulnerabilities
- Attacks using protocol weaknesses
- DoS / DDoS attacks Eve/Mallory
30. Alice
Safeguarding Against Attacks
Server Bob
Administrative Security
- Security & privacy policy
- Governance of security risk management & response
- Uniform enforcement of policy & monitoring
- Disaster recovery planning (DRP) & Business continuity
planning/management (BCP/BCM)
- Legal obligations, requirements & disclaimers
31. Alice
Safeguarding Against Attacks
Server Bob
Physical Security
- Protecting physical access of clients & servers
- Locks & chains, locked rooms, security cameras
- Mobile device security
- Secure storage & secure disposition of storage devices
32. Alice
Safeguarding Against Attacks
Server Bob
User Security
- User account management
- Strong p/w policy (length, complexity, expiry, no meaning)
- Principle of Least Privilege
- “Clear desk, clear screen policy”
- Audit trails
- Education, awareness building & policy enforcement
- Alerts & education about phishing & social engineering
33. Alice
Safeguarding Against Attacks
Server Bob
System Security
- Antivirus, antispyware, personal firewall, intrusion
detection/prevention system (IDS/IPS), log files, monitoring
- Updates, patches, fixes of operating system vulnerabilities &
application vulnerabilities
- Redundancy (avoid “Single Point of Failure”)
- Honeypots
34. Alice
Safeguarding Against Attacks
Server Bob
Software Security
- Software (clients & servers) that is secure by design
- Software testing against failures, bugs, invalid inputs,
performance issues & attacks
- Updates to patch vulnerabilities
35. Alice
Safeguarding Against Attacks
Server Bob
Network Security
- Access control (physical & electronic) to network devices
- Use of secure network protocols if possible
- Data encryption during transit if possible
- Bandwidth monitoring & control
36. Alice
Safeguarding Against Attacks
Server Bob
Database Security
- Access control to databases & storage devices
- Encryption of data stored in databases if necessary
- Secure destruction of data after use
- Access control to queries/reports
- Security features of database management systems (DBMS)
40. Access control
Selective restriction of access to the system
Role-based access control
Access control based on the person’s role
(rather than identity)
Audit trails
Logs/records that provide evidence of
sequence of activities
User Security
41. Identification
Identifying who you are
Usually done by user IDs or some other unique codes
Authentication
Confirming that you truly are who you identify
Usually done by keys, PIN, passwords or biometrics
Authorization
Specifying/verifying how much you have access
Determined based on system owner’s policy & system
configurations
“Principle of Least Privilege”
User Security
42. Nonrepudiation
Proving integrity, origin, & performer of an
activity without the person’s ability to refute
his actions
Most common form: signatures
Electronic signatures offer varying degrees of
nonrepudiation
PIN/password vs. biometrics
Digital certificates (in public key
infrastructure - PKI) often used to ascertain
nonrepudiation
User Security
43. Multiple-Factor Authentication
Two-Factor Authentication
Use of multiple means (“factors”) for authentication
Types of Authentication Factors
Something you know
Password, PIN, etc.
Something you have
Keys, cards, tokens, devices (e.g. mobile phones)
Something you are
Biometrics
User Security
44. Need for Strong Password Policy
So, two informaticians
walk into a bar...
The bouncer says,
"What's the password."
One says, "Password?"
The bouncer lets them
in.
Credits: @RossMartin & AMIA (2012)
45. Recommended Password Policy
Length
8 characters or more (to slow down brute-force attacks)
Complexity (to slow down brute-force attacks)
Consists of 3 of 4 categories of characters
Uppercase letters
Lowercase letters
Numbers
Symbols (except symbols that have special uses by the
system or that can be used to hack system, e.g. SQL Injection)
No meaning (“Dictionary Attacks”)
Not simple patterns (12345678, 11111111) (to slow down brute-
force attacks & prevent dictionary attacks)
Not easy to guess (birthday, family names, etc.) (to prevent
unknown & known persons from guessing)
Personal opinion. No legal responsibility assumed.
46. Recommended Password Policy
Expiration (to make brute-force attacks not possible)
6-8 months
Decreasing over time because of increasing computer’s
speed
But be careful! Too short duration will force users to write
passwords down
Secure password storage in database or system
(encrypted or store only password hashes)
Secure password confirmation
Secure “forget password” policy
Different password for each account. Create variations
to help remember. If not possible, have different sets of
accounts for differing security needs (e.g., bank
accounts vs. social media sites) Personal opinion. No legal responsibility assumed.
49. Techniques to Remember Passwords
http://www.wikihow.com/Create-a-Password-You-Can-
Remember
Note that some of the techniques are less secure!
One easy & secure way: password mnemonic
Think of a full sentence that you can remember
Ideally the sentence should have 8 or more words, with
numbers and symbols
Use first character of each word as password
Sentence: I love reading all 7 Harry Potter books!
Password: Ilra7HPb!
Voila!
Personal opinion. No legal responsibility assumed.
63. Poor grammar
Lots of typos
Trying very hard to convince you to open
attachment, click on link, or reply without
enough detail
May appear to be from known person (rely on
trust & innocence)
Signs of a Phishing Attack
64. Don’t be too trusting of people
Always be suspicious & alert
An e-mail with your friend’s name & info doesn’t have
to come from him/her
Look for signs of phishing attacks
Don’t open attachments unless you expect them
Scan for viruses before opening attachments
Don’t click links in e-mail. Directly type in browser
using known & trusted URLs
Especially cautioned if ask for passwords, bank
accounts, credit card numbers, social security numbers,
etc.
Ways to Protect against Phishing
68. Most common reason for security bugs is
invalid programming assumptions that
attackers will look for
Weak input checking
Buffer overflow
Integer overflow
Race condition (Time of Check / Time of
Use vulnerabilities)
Running programs in new environments
Software Security
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
69. Consider a log-in form on a web page
Example of Weak Input Checking:
SQL Injection
Source code would look
something like this:
statement = "SELECT * FROM users
WHERE name = '" + userName + "';"
Attacker would enter as username:
' or '1'='1
Which leads to this always-true query:
statement = "SELECT * FROM users
WHERE name = '" + "' or '1'='1" + "';"
statement = "SELECT * FROM users WHERE name = '' or '1'='1';"
http://en.wikipedia.org/wiki/SQL_injection
70. Defense in Depth
Multiple layers of security defense are placed
throughout a system to provide redundancy
in the event a security control fails
Secure the weakest link
Promote privacy
Trust no one
Some Security Principles
Saltzer & Schroeder (1975), Viega & McGraw (2000)
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
http://en.wikipedia.org/wiki/Defense_in_depth_(computing)
71. Modular design
Check error conditions on return values
Validate inputs (whitelist vs. blacklist)
Avoid infinite loops, memory leaks
Check for integer overflows
Language/library choices
Development processes
Secure Software Best Practices
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
73. Goal: provide a secure channel between Alice & Bob
A secure channel
Leaks no information about its contents
Delivers only messages from Alice & Bob
Delivers messages in order or not at all
Cryptography
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
Alice Bob
Eve
74. Use of keys to convert plaintext into
ciphertext
Secret keys only Alice & Bob know
History: Caesar’s cipher, substitution
cipher, polyalphabetic rotation
Use of keys and some generator function to
create random-looking strings (e.g. stream
ciphers, block ciphers)
Cryptography
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
75. Encryption Using Secret Key
(Symmetric Cryptography)
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
Alice BobEve
1. Encrypt message using secret key
2. Send encrypted message to Bob
3. Decrypt message
using same secret
key
Eve doesn’t know secret key
(but there are various ways to discover the key)
76. What if no shared secret exists?
Public-key cryptography
Each publishes public key publicly
Each keep secret key secret
Use arithmetic to encrypt & decrypt
message
Cryptography
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
77. Public-Key Cryptography
(Asymmetric Cryptography)
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
Alice BobEve
1. Obtains Bob’s public key from public server
2. Use Bob’s public key to encrypt message
3. Send encrypted message to Bob
Even if Eve knows public key, can’t discover
message (unless weakness in algorithm)
4. Decrypt message using
own private key
78. Digital Signatures
Adapted from Nicholas Hopper’s teaching slides for UMN Computer Security Class Fall 2006 CSCI 5271
Alice Bob
1. Sign message using own private key
2. Send plaintext and random-looking string
(digital signature) to Bob
Provides nonrepudiation
3. Use Alice’s public key
against plaintext received
to get digital signature
4. Compare to match
Alice’s digital signature
received against
signature obtained in #3
81. Virus
Propagating malware that requires user action
to propagate
Infects executable files, data files with
executable contents (e.g. Macro), boot sectors
Worm
Self-propagating malware
Trojan
A legitimate program with additional, hidden
functionality
Malware
82. Spyware
Trojan that spies for & steals personal
information
Logic Bomb/Time Bomb
Malware that triggers under certain conditions
Backdoor/Trapdoor
A hole left behind by malware for future access
Malware
83. Rogue Antispyware (Ransomware)
Software that tricks or forces users to pay before fixing
(real or hoax) spyware detected
Rootkit
A stealth program designed to hide existence of
certain processes or programs from detection
Botnet
A collection of Internet-connected computers that have
been compromised (bots) which controller of the
botnet can use to do something (e.g. do DDoS attacks)
Malware
84. Installed & updated antivirus, antispyware, &
personal firewall
Check for known signatures
Check for improper file changes (integrity failures)
Check for generic patterns of malware (for unknown
malware): “Heuristics scan”
Firewall: Block certain network traffic in and out
Sandboxing
Network monitoring & containment
User education
Software patches, more secure protocols
Defense Against Malware
85. Social media spams/scams/clickjacking
Social media privacy issues
User privacy settings
Location services
Mobile device malware & other privacy risks
Stuxnet (advanced malware targeting certain
countries)
Advanced persistent threats (APT) by
governments & corporations against specific
targets
Newer Threats
87. • ISO/IEC 27000 — Information security management systems — Overview and
vocabulary
• ISO/IEC 27001 — Information security management systems — Requirements
• ISO/IEC 27002 — Code of practice for information security management
• ISO/IEC 27003 — Information security management system implementation guidance
• ISO/IEC 27004 — Information security management — Measurement
• ISO/IEC 27005 — Information security risk management
• ISO/IEC 27031 — Guidelines for information and communications technology readiness
for business continuity
• ISO/IEC 27032 — Guideline for cybersecurity (essentially, 'being a good neighbor' on
the Internet)
• ISO/IEC 27033-1 — Network security overview and concepts
• ISO/IEC 27033-2 — Guidelines for the design and implementation of network security
• ISO/IEC 27033-3:2010 — Reference networking scenarios - Threats, design techniques
and control issues
• ISO/IEC 27034 — Guideline for application security
• ISO/IEC 27035 — Security incident management
• ISO 27799 — Information security management in health using ISO/IEC 27002
Some Information Security Standards
88. US-CERT
U.S. Computer Emergency Readiness Team
http://www.us-cert.gov/
Subscribe to alerts & news
Microsoft Security Resources
http://technet.microsoft.com/en-us/security
http://technet.microsoft.com/en-
us/security/bulletin
Common Vulnerabilities & Exposures
http://cve.mitre.org/
More Information
90. Respect for Persons (Autonomy)
Beneficence
Justice
Non-maleficence
Ethical Principles in Bioethics
91. Hippocratic Oath
...
What I may see or hear in the course of
treatment or even outside of the
treatment in regard to the life of men,
which on no account one must spread
abroad, I will keep myself holding such
things shameful to be spoken about.
...
http://en.wikipedia.org/wiki/Hippocratic_Oath
94. Health Insurance Portability and Accountability Act of
1996 http://www.gpo.gov/fdsys/pkg/PLAW-
104publ191/pdf/PLAW-104publ191.pdf
More stringent state privacy laws apply
HIPAA Goals
To protect health insurance coverage for workers &
families when they change or lose jobs (Title I)
To require establishment of national standards for
electronic health care transactions and national
identifiers for providers, health insurance plans, and
employers (Title II: “Administrative Simplification”
provisions)
Administrative Simplification provisions also address
security & privacy of health data
U.S. Health Information Privacy Law
http://en.wikipedia.org/wiki/Health_Insurance_Portability_and_Accountability_Act
95. Title I: Health Care Access, Portability, and
Renewability
Title II: Preventing Health Care Fraud and
Abuse; Administrative Simplification;
Medical Liability Reform
Requires Department of Health & Human
Services (HHS) to draft rules aimed at increasing
efficiency of health care system by creating
standards for use and dissemination of health
care information
HIPAA (U.S.)
96. Title III: Tax-Related Health Provisions
Title IV: Application and Enforcement
of Group Health Plan Requirements
Title V: Revenue Offsets
HIPAA (U.S.)
98. Covered Entities
A health plan
A health care clearinghouse
A healthcare provider who transmits any health
information in electronic form in connection with a
transaction to enable health information to be exchanged
electronically
Business Associates
Some HIPAA Definitions
99. Protected Health Information (PHI)
Individually identifiable health information transmitted or
maintained in electronic media or other form or medium
Individually Identifiable Health Information
Any information, including demographic information collected from
an individual, that—
(A) is created or received by a CE; and
(B) relates to the past, present, or future physical
or mental health or condition of an individual, the provision of
health care to an individual, or the past, present, or future payment
for the provision of health care to an individual, and—
(i) identifies the individual; or
(ii) with respect to which there is a reasonable basis to believe that
the information can be used to identify the individual.
Some HIPAA Definitions
100. Name
Address
Phone number
Fax number
E-mail address
SSN
Birthdate
Medical Record No.
Health Plan ID
Treatment date
Account No.
Certificate/License No.
Device ID No.
Vehicle ID No.
Drivers license No.
URL
IP Address
Biometric identifier
including fingerprints
Full face photo
Protected Health Information –
Personal Identifiers in PHI
101. Establishes national standards to protect PHI; applies to CE &
business associates
Requires appropriate safeguards to protect privacy of PHI
Sets limits & conditions on uses & disclosures that may be made
without patient authorization
Gives patients rights over their health information, including
rights to examine & obtain copy of health records & to request
corrections
HIPAA Privacy Rule
http://www.hhs.gov/ocr/privacy/hipaa/administrative/privacyrule/index.html
102. Timeline
November 3, 1999 Proposed Privacy Rule
December 28, 2000 Final Privacy Rule
August 14, 2002 Modifications to Privacy Rule
April 14, 2003 Compliance Date for most CE
Full text (as amended)
http://www.hhs.gov/ocr/privacy/hipaa/administrative/privacyrule/
adminsimpregtext.pdf
HIPAA Privacy Rule
http://www.hhs.gov/ocr/privacy/hipaa/administrative/privacyrule/index.html
103. Some permitted uses and disclosures
Use of PHI
Sharing, application, use, examination or
analysis within the entity that maintains the
PHI
Disclosure of PHI
Release or divulgence of information by an
entity to persons or organizations outside of
that entity.
HIPAA Privacy Rule
104. A covered entity may not use or disclose
PHI, except
with individual consent for treatment,
payment or healthcare operations (TPO)
with individual authorization for other
purposes
without consent or authorization for
governmental and other specified
purposes
HIPAA Privacy Rule
105. Treatment, payment, health care operations
(TPO)
Quality improvement
Competency assurance
Medical reviews & audits
Insurance functions
Business planning & administration
General administrative activities
HIPAA Privacy Rule
106. Uses & disclosures without the need for patient
authorization permitted in some circumstances
Required by law
For public health activities
About victims of abuse, neglect, or domestic
violence
For health oversight activities
For judicial & administrative proceedings
For law enforcement purposes
About decedents
HIPAA Privacy Rule
107. Uses & disclosures without the need for patient
authorization permitted in some circumstances
For cadaveric organ, eye, or tissue donation purposes
For research purposes
To avert a serious threat to health or safety
For workers’ compensation
For specialized government functions
Military & veterans activities
National security & intelligence activities
Protective services for President & others
Medical suitability determinants
Correctional institutions
CE that are government programs providing public benefits
HIPAA Privacy Rule
108. Control use and disclosure of PHI
Notify patients of information practices (NPP, Notice of Privacy
Practices)
Specifies how CE can use and share PHI
Specifies patient’s rights regarding their PHI
Provide means for patients to access their own record
Obtain authorization for non-TPO uses and disclosures
Log disclosures
Restrict use or disclosures
Minimum necessary
Privacy policy and practices
Business Associate agreements
Other applicable statutes
Provide management oversight and response to minimize threats and
breaches of privacy
Responsibilities of a CE
From a teaching slide in UMN’s Spring 2006 Health Informatics II class by Dr. David Pieczkiewicz
109. Individually identifiable health information
collected and used solely for research IS NOT PHI
Researchers obtaining PHI from a CE must obtain
the subject’s authorization or must justify an
exception:
Waiver of authorization (obtain from the IRB)
Limited Data Set (with data use agreement)
De-identified Data Set
HIPAA Privacy supplements the Common Rule
and the FDA’s existing protection for human
subjects
HIPAA & Research
From a teaching slide in UMN’s Spring 2006 Health Informatics II class by Dr. David Pieczkiewicz
110. De-identified Data Set
Remove all 18 personal identifiers of subjects,
relatives, employers, or household members
OR biostatistician confirms that individual cannot be
identified with the available information
Limited Data Set
May include Zip, Birthdate, Date of death, date of
service, geographic subdivision
Remove all other personal identifiers of subject, etc.
Data Use Agreement signed by data recipient that
there will be no attempt to re-identify the subject
Research Data Sets
From a teaching slide in UMN’s Spring 2006 Health Informatics II class by Dr. David Pieczkiewicz
111. Assure the CE that all research-initiated HIPAA
requirements have been met
Provide letter of approval to the researcher to
conduct research using PHI
OR, Certify and document that waiver of
authorization criteria have been met
Review and approve all authorizations and data
use agreements
Retain records documenting HIPAA actions for 6
years
IRB’s New Responsibility
From a teaching slide in UMN’s Spring 2006 Health Informatics II class by Dr. David Pieczkiewicz
112. Establishes national standards to protect
individuals’ electronic PHI that is created,
received, used, or maintained by a CE.
Requires appropriate safeguards to ensure
confidentiality, integrity & security of
electronic PHI
Administrative safeguards
Physical safeguards
Technical safeguards
HIPAA Security Rule
http://www.hhs.gov/ocr/privacy/hipaa/administrative/privacyrule/index.html
113. Timeline
August 12, 1998 Proposed Security Rule
February 20, 2003 Final Security Rule
April 21, 2005 Compliance Date for most CE
Full Text
http://www.hhs.gov/ocr/privacy/hipaa/
administrative/securityrule/securityrulepdf.pdf
HIPAA Security Rule
http://www.hhs.gov/ocr/privacy/hipaa/administrative/securityrule/index.html
114. The HIPAA Security Rule is:
A set of information security “best practices”
A minimum baseline for security
An outline of what to do, and what procedures
should be in place
The HIPAA Security Rule is not:
A set of specific instructions
A set of rules for universal, unconditional
implementation
A document outlining specific implementations
(vendors, equipment, software, etc.)
HIPAA Security Rule: Meaning
From a teaching slide in UMN’s Spring 2006 Health Informatics II class by Dr. David Pieczkiewicz
115. Many rules are either Required or Addressable
Required:
Compliance is mandatory
Addressable:
If a specification in the Rule is reasonable and
appropriate for the CE, then the CE must implement
Otherwise, documentation must be made of the
reasons the policy cannot/will not be implemented,
and when necessary, offer an alternative
HIPAA Security Rule: Meaning
From a teaching slide in UMN’s Spring 2006 Health Informatics II class by Dr. David Pieczkiewicz
116. Breach notification
Extension of complete Privacy & Security
HIPAA provisions to business associates of
covered entities
New rules for accounting of disclosures of a
patient’s health information
New in HITECH Act of 2009
117. Conflicts between federal vs. state laws
Variations among state laws of different
states
HIPAA only covers “covered entities”
No general privacy laws in place, only a few
sectoral privacy laws e.g. HIPAA
Health Information Privacy Law:
U.S. Challenges
118. Canada - The Privacy Act (1983), Personal
Information Protection and Electronic Data
Act of 2000
EU Countries - EU Data Protection Directive
UK - Data Protection Act 1998
Austria - Data Protection Act 2000
Australia - Privacy Act of 1988
Germany - Federal Data Protection Act of
2001
Health Information Privacy Law:
Other Western Countries
121. The Official Information Act, B.E. 2540
พรบ.ข้อมูลข่ำวสำรของรำชกำร พ.ศ. 2540
“เปิดเผยเป็นหลัก ปกปิดเป็นข้อยกเว้น”
“มาตรา 15 ข้อมูลข่าวสารของราชการที่มีลักษณะอย่างหนึ่งอย่างใดดังต่อไปนี้
หน่วยงานของรัฐหรือเจ้าหน้าที่ของรัฐอาจมีคาสั่งมิให้เปิดเผยก็ได้ โดยคานึงถึง
การปฏิบัติหน้าที่ตามกฎหมาย...ประกอบกัน
...
(5) รายงานการแพทย์หรือข้อมูลข่าวสารส่วนบุคคลซึ่งการเปิดเผยจะเป็นการรุก
ล้าสิทธิส่วนบุคคลโดยไม่สมควร
(6) ข้อมูลข่าวสารของราชการที่มีกฎหมายคุ้มครองมิให้เปิดเผย...
...”
Thai Privacy Laws
122. No universal personal data privacy law
(Draft law has been proposed)
National Health Act, B.E. 2550
พรบ.สุขภาพแห่งชาติ พ.ศ. 2550
“มาตรา 7 ข้อมูลด้านสุขภาพของบุคคล เป็นความลับส่วนบุคคล
ผู้ใดจะนาไปเปิดเผยในประการที่น่าจะทาให้บุคคลนั้นเสียหายไม่ได้
เว้นแต่การเปิดเผยนั้นเป็นไปตามความประสงค์ของบุคคลนั้น
โดยตรง หรือมีกฎหมายเฉพาะบัญญัติให้ต้องเปิดเผย แต่ไม่ว่าใน
กรณีใด ๆ ผู้ใดจะอาศัยอานาจหรือสิทธิตามกฎหมายว่าด้วยข้อมูล
ข่าวสารของราชการหรือกฎหมายอื่นเพื่อขอเอกสารเกี่ยวกับข้อมูล
ด้านสุขภาพของบุคคลที่ไม่ใช่ของตนไม่ได้”
Thai Privacy Laws
123. Computer-Related Crimes Act, B.E. 2550
พรบ.การกระทาความผิดเกี่ยวกับคอมพิวเตอร์ พ.ศ. 2550
กำหนดกำรกระทำที่ถือเป็นควำมผิด และหน้ำที่ของผู้
ให้บริกำร
Focuses on prosecuting computer
crimes & computer-related crimes
Responsibility of organizations as IT
service provider: Logging &
provision of access data to authorities
Thai ICT Laws
138. แบ่งเป็น 11 หมวด (Domains)
Security policy
Organization of information security
Asset management
Human resources security
Physical and environmental security
Communications and operations management
Access control
Information systems acquisition, development and
maintenance
Information security incident management
Business continuity management
Regulatory compliance
มาตรฐาน Security ตามวิธีการแบบปลอดภัย
140. Official Information Act only covers
governmental organizations
“Disclose as a rule, protect as an exception”
not appropriate mindset for health
information
National Health Act: One blanket provision
with minimal exceptions: raising concerns
about enforceability (in exceptional
circumstances, e.g. disasters)
Health Information Privacy Law:
Thailand’s Challenges
141. No general data privacy law in place
ICT laws (e.g. Electronic Transactions Act)
focus on security & privacy in general (no
specific health-related provisions)
Governance: No governmental authority
responsible for oversight, enforcement &
regulation of health information privacy
protections
Policy: No systematic national policy to
promote privacy protections
Health Information Privacy Law:
Thailand’s Challenges
142. Each country has its unique context,
including legal systems, national priorities,
public mindset, and infrastructure
A comprehensive & systematic approach to
data privacy and health information privacy
is still lacking in some countries such as
Thailand
Key issues include public awareness,
enforceable regulations, governance, and
national policy
Health Information Privacy Law:
Summary