|
|
|
Domain-Specific Applications (4 of 5) |
|
-
The HIPAA regulations have imposed unprecedented controls
on the treatment of identifiers, codes, and patient-identifiable
clinical data. Healthcare provider organizations have already
begun to go down the familiar road of "pay each vendor
for the upgrade that complies". But there is a better
way, based on sound architecture and rational factoring
of complexity.
The
CC continuously correlates all stakeholder IDs including
user ids to enterprise master IDs, so that policy logic
cannot be circumvented by identifier incomparability. The
same CC product probabilistically indexes Patients, Doctors,
Guarantors, Employees, Faculty, Students, and users with
no lines of deployment code.
The AC security framework provides one of the world's few
implementations of the world's only object-based API
standard for fine-grained access control. PKI stops
at identification and authentication, with no access control.
Role-based access controls, JSM, and LDAP facilities can
protect operations and coarse-grained data objects based
on credentials. But only the RAD standard describes how
to filter query result sets based on the sensitivities and
stewardships of the data in connection with the credentials
of the user. This framework allows for the installation
of policy evaluators at all levels (Federal, State, Enterprise,
Individual authorizations and role/purpose) and facilitates
the correct policy interactions when multiple policies apply.
|
| The
AC security framework provides one of the world's few implementations
of the world's only object-based API standard for fine-grained
access control. |
|
|
|
