Now the user has a defined role for viewing information. Through the GUI, the user can perform all actions she is authorized to perform in her current role. The user logs off after completing her work. Patients can see an audit trail showing who has looked at their medical records and who is allowed to do so. The message doesn't explain the nature of the change, just that a change has occurred.
Patients can select how frequently they want to be notified about changes.
These user data are sent to authenticated and authorized users via the Internet. This architecture combines secure Web services, a trusted application server, and secure administration services to ensure that access to certain information is restricted to authorized individuals. The Web server then sends back the Java applet, which from that point on communicates only with the trusted application server. This server receives the user's requests, determines what data they can see and what actions they can perform and returns the results. In addition, the label-based control separates and protects the integrity of executable code, according to how critical the code is to system security and operations.