Difference between revisions of "How does VistA work"

From VistApedia
Jump to: navigation, search
m (typo corrections + minor edits)
Line 1: Line 1:
This page decribes the basic CPRS/VistA model. This will not be much more than a picture.  
+
This page describes the basic CPRS/VistA model. This will not be much more than a picture.  
  
 
-FT
 
-FT
Line 8: Line 8:
 
# CPRS uses a part of a person's own computer called the [[RPC Client]].
 
# CPRS uses a part of a person's own computer called the [[RPC Client]].
 
# The RPC Client uses the computer's network software and hardware to establish a link to some bigger computer running the VistA server.  The part of the VistA server that the RPC Client connects to is called the RPC Broker.
 
# The RPC Client uses the computer's network software and hardware to establish a link to some bigger computer running the VistA server.  The part of the VistA server that the RPC Client connects to is called the RPC Broker.
# The RPC Broker sets up a part of the VistA server to handle any questions and answers that are needed by the original person's CPRS session. This could be called the user's RPC proxy.
+
# The RPC Broker sets up a part of the VistA server to handle any questions and answers that are needed by the person's CPRS session. This could be called the user's RPC proxy.
# CPRS on the person's PC uses the RPC client to send requests to the VistA server, which replies with answers.   
+
# CPRS uses the RPC client on the person's PC to send requests to the RPC proxy on the VistA server. The proxy forwards questions to VistA and VistA replies with answers.   
 
## An example request might be "I am this person, authorize me."
 
## An example request might be "I am this person, authorize me."
 
## The RPC proxy then uses the access code and verify code which was sent with the request, and tries to authorize that person's CPRS.   
 
## The RPC proxy then uses the access code and verify code which was sent with the request, and tries to authorize that person's CPRS.   
### If it succeeds, then other requests can be answered by the proxy.
+
### If it succeeds, then other requests can be answered through the proxy.
 
### If it does not succeed, then the proxy waits for a proper authorized user.
 
### If it does not succeed, then the proxy waits for a proper authorized user.
 
# Eventually, the person using CPRS finishes with their work, and the RPC proxy on the VistA server doesn't get any requests for a while.  The VistA server then removes the proxy and the connection is broken.
 
# Eventually, the person using CPRS finishes with their work, and the RPC proxy on the VistA server doesn't get any requests for a while.  The VistA server then removes the proxy and the connection is broken.

Revision as of 21:07, 26 January 2009

This page describes the basic CPRS/VistA model. This will not be much more than a picture.

-FT

This isn't a picture, but generally,

  1. CPRS runs on a person's own computer.
  2. CPRS uses a part of a person's own computer called the RPC Client.
  3. The RPC Client uses the computer's network software and hardware to establish a link to some bigger computer running the VistA server. The part of the VistA server that the RPC Client connects to is called the RPC Broker.
  4. The RPC Broker sets up a part of the VistA server to handle any questions and answers that are needed by the person's CPRS session. This could be called the user's RPC proxy.
  5. CPRS uses the RPC client on the person's PC to send requests to the RPC proxy on the VistA server. The proxy forwards questions to VistA and VistA replies with answers.
    1. An example request might be "I am this person, authorize me."
    2. The RPC proxy then uses the access code and verify code which was sent with the request, and tries to authorize that person's CPRS.
      1. If it succeeds, then other requests can be answered through the proxy.
      2. If it does not succeed, then the proxy waits for a proper authorized user.
  6. Eventually, the person using CPRS finishes with their work, and the RPC proxy on the VistA server doesn't get any requests for a while. The VistA server then removes the proxy and the connection is broken.