Difference between revisions of "Clinical Procedures"

From VistApedia
Jump to: navigation, search
(Clinical Procedures)
Line 1: Line 1:
 
== Clinical Procedures ==
 
== Clinical Procedures ==
  
* There is a Clinical Procedures GUI program named "CPUSER.exe". It is a [[MS Windows]] application.
+
* There is a Clinical Procedures GUI program named "CPUSER.exe" OR "CPUser.exe". It is a [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "CPMANAGER.EXE". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "CPMANAGER.EXE". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "CPFLOWSHEETS.EXE". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "CPFLOWSHEETS.EXE". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "HEMODIALYSIS.EXE". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "HEMODIALYSIS.EXE". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "CPGatewayService.exe". It is an [[MS Windows]] application.
 
* There is a Clinical Procedures GUI program named "CPGatewayService.exe". It is an [[MS Windows]] application.
 
+
* There is a Clinical Procedures GUI program named "CPConsole.exe". It is an [[MS Windows]] application.
 
=== Organization of system ===
 
=== Organization of system ===
  
Line 27: Line 27:
  
 
Clinical Procedures receives results from some testing machines as PDF Files.
 
Clinical Procedures receives results from some testing machines as PDF Files.
 +
=== CP Gateway Service ===
 +
 +
The CP Gateway Service is the component that processes HL7 messages.
 +
The CP Gateway Service is composed of two subsystems.  One CP Gateway Service subsystem exists solely within VistA.
 +
One CP Gateway Service is a [[MS Windows]] service that interacts with VistA via the RPC Broker.
 +
A vendor device sends an observation to VistA inside an HL7 (ORU^R01) inbound message.
 +
The VA FileMan [[FILE HL7 EVENT TYPE CODE]] ([[FILE 779.001]]) has an entry for an ORU event. The ORU message is defined as an entry in the [[FILE HL7 MESSAGE TYPE]] ([[FILE 771.2]]) with the full name of "Observ result/unsolicited".

Revision as of 21:55, 9 July 2018

Clinical Procedures

  • There is a Clinical Procedures GUI program named "CPUSER.exe" OR "CPUser.exe". It is a MS Windows application.
  • There is a Clinical Procedures GUI program named "CPMANAGER.EXE". It is an MS Windows application.
  • There is a Clinical Procedures GUI program named "CPFLOWSHEETS.EXE". It is an MS Windows application.
  • There is a Clinical Procedures GUI program named "HEMODIALYSIS.EXE". It is an MS Windows application.
  • There is a Clinical Procedures GUI program named "CPGatewayService.exe". It is an MS Windows application.
  • There is a Clinical Procedures GUI program named "CPConsole.exe". It is an MS Windows application.

Organization of system

Clinical Procedures (many times abbreviated as "CP" and in the namespace of "

Clinical Procedures is a software package developed as a "National" class.

Clinical Procedures has several components each of which has an instance at a VistA site.

One component of Clinical Procedures communicates with the main VistA instance for the site.

This component using TCP/IP and the RPC Broker to communicate data and request remote procedure calls.

A different component communicates with machines which provide cardiac tests for patients.

A different component communicates with the VistA Imaging computer for the site.

The Clinical Procedures system stores PDF Files in the VistA Imaging system. The VistA Imaging system stores PDF Files from Clinical Procedures.

Clinical Procedures receives results from some testing machines as PDF Files.

CP Gateway Service

The CP Gateway Service is the component that processes HL7 messages. The CP Gateway Service is composed of two subsystems. One CP Gateway Service subsystem exists solely within VistA. One CP Gateway Service is a MS Windows service that interacts with VistA via the RPC Broker. A vendor device sends an observation to VistA inside an HL7 (ORU^R01) inbound message. The VA FileMan FILE HL7 EVENT TYPE CODE (FILE 779.001) has an entry for an ORU event. The ORU message is defined as an entry in the FILE HL7 MESSAGE TYPE (FILE 771.2) with the full name of "Observ result/unsolicited".