ProjectSend
-
@Dashrender said:
You are basically saying that a Covered Entity can't decide that they want to do this, and do it... and I'd like to know why you feel that way?
I feel this way because it is my understanding of the law and the only way that the law makes sense. Why would ANY unnecessary use or unauthorized use of my private data be allowed when we are talking about a law specifically to stop the unnecessary and unauthorized use of that data?
-
@Dashrender said:
Also, why do you feel that puts you at more risk?
What is the risk that HIPAA is to protect against? Unnecessary people getting access to my data.
What has happened? Exactly that.
-
@scottalanmiller said:
@Dashrender said:
You are basically saying that a Covered Entity can't decide that they want to do this, and do it... and I'd like to know why you feel that way?
I feel this way because it is my understanding of the law and the only way that the law makes sense. Why would ANY unnecessary use or unauthorized use of my private data be allowed when we are talking about a law specifically to stop the unnecessary and unauthorized use of that data?
Just because you consider it unnecessary does not mean others don't. You consider this entire approach pointless boarding on meaningless, I simply don't agree.
Again, and I'll continue to state this, I would never do as @dafyre suggested and call patients based on an IP seeming to be coming from a bad location.
-
@Dashrender said:
Just because you consider it unnecessary does not mean others don't. You consider this entire approach pointless boarding on meaningless, I simply don't agree.
But... is it your call at all? It's not your data. Why would you have an association with the data at all?
-
@Dashrender said:
Again, and I'll continue to state this, I would never do as @dafyre suggested and call patients based on an IP seeming to be coming from a bad location.
So how would you use it, then?
-
And more importantly.... why?
-
@Dashrender said:
Again, and I'll continue to state this, I would never do as @dafyre suggested and call patients based on an IP seeming to be coming from a bad location.
I never suggested I'd be calling patients. Only employees of the company that I work for.
-
@dafyre said:
@Dashrender said:
Again, and I'll continue to state this, I would never do as @dafyre suggested and call patients based on an IP seeming to be coming from a bad location.
I never suggested I'd be calling patients. Only employees of the company that I work for.
My mistake.
-
@Dashrender 8-) --
But this is one of the reasons that IT can be such a complicated field. You get ten different people talking about the same thing, you get three rabbit holes, 2 topics, and a whole mess of confusion, lol.
-
Agreed.
When it comes to direct patient access, I probably wouldn't care where they access it from, and if I could skip all tracking of that I might consider it. That said who's to blame if a patients account is accessed using their credentials and the account holder didn't authorize it? The Covered Entity (CE)?
-
@Dashrender said:
Agreed.
When it comes to direct patient access, I probably wouldn't care where they access it from, and if I could skip all tracking of that I might consider it. That said who's to blame if a patients account is accessed using their credentials and the account holder didn't authorize it? The Covered Entity (CE)?
Is that true even if they have their own account and someone authenticated as them? I'm am unaware of any such liability when proper precautions are taken.
-
@Reid-Cooper said:
nd want to talk
No. If I wrote this it would be written in MVC for PHP. I was looking for an open source solution, found one and feel it needs some tweaks but its a good solution overall.
-
@scottalanmiller said:
he web logs for MangoLassi would tell us almost nothing. It would show only one connection for each tab that you have open rather than info about each page that you go to. That's why we rely on the application itself for stats. Only the app knows when it has shown a p
I noticed this right away when I came to MLIT because the views tick at each view instead of unique views.
-
@dafyre I havent felt out the product yet, but I did install centOS into a vm last night, then installed nethserver and owncloud to check it all out. I still like this ProjectSend open source solution though.
-
@Dashrender said:
" it can run using its own stand-alone user database or run using LDAP / AD for the User database. "I wouldnt want to tie it into AD except for system users. Client users (remote users) should not have accounts in my AD because thats one more thing I have to worry about.
-
@scottalanmiller said:
@coliver said:
So if the user is liable for their own account why are you tracking IP addresses? You just said after you give them the information you are no longer responsible for how they access it.
I'd say tracking IPs is bad because there is nothing good that could come from storing that information.
Tracking IP's is not bad, but its not entirely reliable unless you make a reverse proxy connection.
-
@drewlander said:
@scottalanmiller said:
@coliver said:
So if the user is liable for their own account why are you tracking IP addresses? You just said after you give them the information you are no longer responsible for how they access it.
I'd say tracking IPs is bad because there is nothing good that could come from storing that information.
Tracking IP's is not bad, but its not entirely reliable unless you make a reverse proxy connection.
I meant in a context of HIPAA data. As a HIPAA compliant facility, you want to avoid having any data that you are not required to have. Holding data equals holding liability.
-
@scottalanmiller said:
Things you cannot know:
- That the IP is from Japan
- That the person is not supposed to be in Japan
You know neither of these things. How do you want to react with misleading information that makes you assume one thing but doesn't mean that?
I geoblock in my firewall, so I assure you any IP assigned to Japan is not making a connection to me. Therefore it is possible to know if traffic is coming from Japan. Unless of course they are going through a proxy or something.
-
@Dashrender said:
LOL, our current EHR company does ban access to their systems from most middle east and chinese based IPs. So yeah, they do deny you. Is it right? who am I to say?If I was McDonald's fast food I would not Geoblock because I would be a multinational company. Athena Healthcare however... No one in Ukraine has any business making a connection so I dont see why they wouldnt block traffic from a foreign country.
-
@drewlander said:
I geoblock in my firewall, so I assure you any IP assigned to Japan is not making a connection to me. Therefore it is possible to know if traffic is coming from Japan. Unless of course they are going through a proxy or something.
There was another thread just today about how @Carnival-Boy's connection is showing him as France, but he is not. There is no reliable geo-location service for IPs today even when we don't VPN or proxy. As someone outside of the US, that stuff is wrong a lot of the time and people choose to appear as different countries intentionally all of the time.
Geo-location blocking is tough because it blocks the good guys and not the bad guys.
