ProjectSend
-
@scottalanmiller said:
Why IP and Phone Numbers are HIPAA Data:
“Individually identifiable health information” is information, including demographic data, that relates to:
the individual’s past, present or future physical or mental health or condition,
the provision of health care to the individual, or
the past, present, or future payment for the provision of health care to the individual,Tracking that information would record information about the provisioning of healthcare.
let's assume that it's provisionable/provisioned data - so what? I work for the company house/managing/maintaining the data, why can't I access it for the sake of security?
-
@Dashrender said:
let's assume that it's provisionable/provisioned data - so what? I work for the company house/managing/maintaining the data, why can't I access it for the sake of security?
Because it is NOT your data, you DO NOT need it and it is against the law. The security to worry about here is IT getting data it does not have a right to see! The security breach here would be you.
The assumption of geo-security is an idea being pushed by IT, and to be useful would require a lot of HIPAA data that is not yours to use.
-
@scottalanmiller said:
@Dashrender said:
let's assume that it's provisionable/provisioned data - so what? I work for the company house/managing/maintaining the data, why can't I access it for the sake of security?
Because it is NOT your data, you DO NOT need it and it is against the law. The security to worry about here is IT getting data it does not have a right to see! The security breach here would be you.
The assumption of geo-security is an idea being pushed by IT, and to be useful would require a lot of HIPAA data that is not yours to use.
I think yours is one of opinion and not rule of law or precedence. But if you have either, I'd love links.
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
let's assume that it's provisionable/provisioned data - so what? I work for the company house/managing/maintaining the data, why can't I access it for the sake of security?
Because it is NOT your data, you DO NOT need it and it is against the law. The security to worry about here is IT getting data it does not have a right to see! The security breach here would be you.
The assumption of geo-security is an idea being pushed by IT, and to be useful would require a lot of HIPAA data that is not yours to use.
I think yours is one of opinion and not rule of law or precedence. But if you have either, I'd love links.
I thought that I provided it. It was quoted right from the HIPAA page itself.
-
From hhs.gov
Basic Principle. A major purpose of the Privacy Rule is to define and limit the circumstances in which an individual’s protected heath information may be used or disclosed by covered entities. A covered entity may not use or disclose protected health information, except either: (1) as the Privacy Rule permits or requires; or (2) as the individual who is the subject of the information (or the individual’s personal representative) authorizes in writing.
-
Required Disclosures. A covered entity must disclose protected health information in only two situations: (a) to individuals (or their personal representatives) specifically when they request access to, or an accounting of disclosures of, their protected health information; and (b) to HHS when it is undertaking a compliance investigation or review or enforcement action.
-
And notice that IT is not even considered a business associate:
Business Associate Defined. In general, a business associate is a person or organization, other than a member of a covered entity's workforce, that performs certain functions or activities on behalf of, or provides certain services to, a covered entity that involve the use or disclosure of individually identifiable health information. Business associate functions or activities on behalf of a covered entity include claims processing, data analysis, utilization review, and billing.9 Business associate services to a covered entity are limited to legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation, or financial services.
-
Access and Uses. For internal uses, a covered entity must develop and implement policies and procedures that restrict access and uses of protected health information based on the specific roles of the members of their workforce. These policies and procedures must identify the persons, or classes of persons, in the workforce who need access to protected health information to carry out their duties, the categories of protected health information to which access is needed, and any conditions under which they need the information to do their jobs.
-
I would say that ANY access by IT (or facilities, or janitorial or decorating) staff is a very clear violation of the intent of the law.
-
Let's think of it in another way.... would you be happy having this conversation with a judge:
"Your honor, I accessed private healthcare data because I felt that I could use that information for the purpose of securing a network that I was managing."
and...
"No, I was not directly told to access this data or to secure the network in this manner."
-
If you were asked the questions that led to those answers, would you feel that the access and potential disclosure of that data was allowed or justified? In the first case, I think HIPAA is violated. In the second, I fear that the "corporate veil" would be pierced and it might become a personal liability rather than a corporate one.
-
@scottalanmiller said:
Let's think of it in another way.... would you be happy having this conversation with a judge:
"Your honor, I accessed private healthcare data because I felt that I could use that information for the purpose of securing a network that I was managing."
and...
"No, I was not directly told to access this data or to secure the network in this manner."
Yes I would, on the assumption that it was part of my purview to protect my network to my own levels. I.E. I am the one who decides what is and isn't needed to protect my network.
-
@Dashrender said:
@scottalanmiller said:
Let's think of it in another way.... would you be happy having this conversation with a judge:
"Your honor, I accessed private healthcare data because I felt that I could use that information for the purpose of securing a network that I was managing."
and...
"No, I was not directly told to access this data or to secure the network in this manner."
Yes I would, on the assumption that it was part of my purview to protect my network to my own levels. I.E. I am the one who decides what is and isn't needed to protect my network.
So you feel that the privacy of HIPAA data is okay to breach if the reason is for protecting YOUR network? I don't believe that a judge would see that in a kind light. Protecting your network, protecting any network, is not something that health data is allowed to be used for.
-
As someone with health data out there, it worries me that people who are entrusted to protect it probably routinely feel their their own security needs would justify the theft and misappropriation of my data for their own, personal uses which is not just wrong on its own, but puts my data at greater risk as it would then be being stored and used outside of HIPAA regulated systems. No one would be looking for that data to be being stored with network records, for example.
-
@scottalanmiller said:
@Dashrender said:
@scottalanmiller said:
Let's think of it in another way.... would you be happy having this conversation with a judge:
"Your honor, I accessed private healthcare data because I felt that I could use that information for the purpose of securing a network that I was managing."
and...
"No, I was not directly told to access this data or to secure the network in this manner."
Yes I would, on the assumption that it was part of my purview to protect my network to my own levels. I.E. I am the one who decides what is and isn't needed to protect my network.
So you feel that the privacy of HIPAA data is okay to breach if the reason is for protecting YOUR network? I don't believe that a judge would see that in a kind light. Protecting your network, protecting any network, is not something that health data is allowed to be used for.
The difference is that I don't consider it a breach. I work for the company that has the data. If said company feels that it's within my job duties to access that data, then I'm allowed to do so. Period.
You were trying to compare IT to a Business Associate (BA) but internal IT is not a BA because it's internal, and therefore falls under the normal coverage of the Covered Entity itself, not a BA.
-
@scottalanmiller said:
As someone with health data out there, it worries me that people who are entrusted to protect it probably routinely feel their their own security needs would justify the theft and misappropriation of my data for their own, personal uses which is not just wrong on its own, but puts my data at greater risk as it would then be being stored and used outside of HIPAA regulated systems. No one would be looking for that data to be being stored with network records, for example.
That was one heck of a leap. Why would you assume for even one second that I would pull the actual data out of the HIPAA controlled system? If the IP's and the phone numbers and the logon IDs are all inside the HIPAA controlled system, why would I need to leave it? Perhaps I could make an external document stating that I made a phone call regarding this information, again something I would never do at this company, but that external data could only refer to say a chart number, but no name or phone number.
-
@Dashrender said:
The difference is that I don't consider it a breach. I work for the company that has the data. If said company feels that it's within my job duties to access that data, then I'm allowed to do so. Period.
That's completely not true. That is anything but a "period." That would simply make managers culpable too. That will would constitute data theft no matter who in that company decided to do so.
-
@Dashrender said:
You were trying to compare IT to a Business Associate (BA) but internal IT is not a BA because it's internal, and therefore falls under the normal coverage of the Covered Entity itself, not a BA.
Are you sure because the mentioned external entities separately.
-
@Dashrender said:
That was one heck of a leap. Why would you assume for even one second that I would pull the actual data out of the HIPAA controlled system?
Because you said that you would use mine (a client's) personally identifiable data that ties me to the facility and provisioning for your own purposes. Only going by what you stated.
-
@Dashrender said:
If the IP's and the phone numbers and the logon IDs are all inside the HIPAA controlled system, why would I need to leave it?
Because it goes to you, you being IT and not being part of the health care delivery system are the breach yourself. You are personally the system outside of the HIPAA control. The point of HIPAA is to restrict who gets access to my records to the people who need it in order to deliver my healthcare, you are not one of those people.
