Use the browser controls to return to previous page

Deployment Over the Net

In this paper we use the word Net in preference to Internet, to emphasize that RightsVault is deployable over the Internet, and Intranets, and Extranets - any network of any scope as long as it uses Internet protocols for communication. The deployment shown in the first diagram in section Integrated System Structure above is typical, but many more configurations are feasible. Lets consider four examples.

RightsMarket, or the Health Info System (HIS) supplier, runs co-located RightsVault (RV) and RightsServer (RS) installations for many small users of the Health Info System (HIS). Many end users of their protected EMRs run the freely available combination of RightsClient and Trusted Tool (RCT). Both server components might be on the same machine.

A large hospital or a regional health authority or an HMO runs all components, including many installations of the HIS and RCT. Outside users of protected hospital records can download from RV using nothing but a Web browser. Their RCT can communicate over the Net to RS to get permissions and track use.

Several small and medium-size users (e.g. private group practices, small hospitals, labs) each run their own RightsVault, but outsource the hosting of the RightsServer to RightsMarket or the HIS supplier.

A lab (or a hospital or a health region) has many records systems and sources of information. It runs its own RightsVault and RightsServer to standardize the authorization and tracking mechanism for all systems and sources. HIS₁ is fully integrated with RightsVault. Users of HIS₁ secure and catalog its EMRs and set permissions through the user interface of HIS₁. HIS₁ operations (patient-specific data accesses, orders, &) are authorized and tracked via RightsVault. HIS₁drives RightsVault through RightsVault APIs.

HIS₂ is not integrated with RightsVault. Users export EMRs from HIS₂ and then protect, catalog and set permissions for the EMRs through a Web interface to RightsVault. Some EMRs are simply typed up using a word processor (WP). These EMRs are protected in the same way as the EMRs of of HIS_2.