|
Posted by ZeldorBlat on 02/13/06 16:45
J wrote:
> Are there any issues with php that would require me not to use php and other
> (mature?) tools in an inhouse app for a medical facility? As far as I can
> tell, reading the hipaa laws, issues like password protection and security
> for internal operations are 'addressable' - you have to see if it's
> appropriate for you. For a small clinic, they don't require, for example,
> separate workstation logons or logging per employee. They only require
> policies defining the handling of the information.
>
> Any warnings?
> -J
PHP, like most programming languages, is very good at doing what you
tell it to. In other words, there's no intrinsic property of PHP (or
C++, or Java, or Ruby, or anything else) that would make appropriate or
inappropriate for building a HIPAA-compliant application. You make or
break the compliance with the application that /you/ build using these
tools.
[Back to original message]
|