CPRS Overview - Revision history

DavidWhitten at 02:52, 4 March 2020

2020-03-04T02:52:46Z

← Older revision		Revision as of 02:52, 4 March 2020
Line 1:		Line 1:
	= Overview of [[CPRS~\|CPRS]] =		= Overview of [[CPRS~\|CPRS]] =

	[[CPRS~\|CPRS]] provides clinicians, managers, support staff, researchers, and others an integrated patient [[record~\|Record]]] system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, ~~[[PCMM~~~\|PCMM]], ~~[[PCE~~~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with [[CPRS~\|CPRS]]. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and [[record~\|Record]]s, as well as an efficient means for others to access and use patient information.		[[CPRS~\|CPRS]] provides clinicians, managers, support staff, researchers, and others an integrated patient [[record~\|Record]]] system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, {{g\|PCMM}}, {{g\|PCE}}, [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with [[CPRS~\|CPRS]]. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and [[record~\|Record]]s, as well as an efficient means for others to access and use patient information.

	== Features: ==		= CPRS Features: =

	=== Smooth transition from OE/RR ===		=== Smooth transition from OE/RR ===
Line 77:		Line 77:
	Select OPTION NAME: OR [[CPRS\|CPRS]] GUI CHART [[CPRS~\|CPRS]]Chart version 1.0.27.83		Select OPTION NAME: OR [[CPRS\|CPRS]] GUI CHART [[CPRS~\|CPRS]]Chart version 1.0.27.83
	Select RPC: ORWPT OTHER-RADIOBUTTONS// <=== ADD THE RPC NAME HERE		Select RPC: ORWPT OTHER-RADIOBUTTONS// <=== ADD THE RPC NAME HERE

			== CPRS Errors ==
			There are times that running CPRSChart.exe in a MS Windows Operating System that an error occurs.
			The page [[CPRS_Error]] helps one search for solutions to these errors.

NeilArmstrong: Added a Glossary link to Consult/Request Tracking~

2013-02-08T20:52:32Z

Added a Glossary link to Consult/Request Tracking~

← Older revision		Revision as of 20:52, 8 February 2013
Line 39:		Line 39:
	Generically written data extraction/storage remote procedure calls (RPCs) provide access to VISTA clinical data for [[CPRS~\|CPRS]] interfaces, VAMC-developed software, and HOST/COTS [[application~\|Application]]s.		Generically written data extraction/storage remote procedure calls (RPCs) provide access to VISTA clinical data for [[CPRS~\|CPRS]] interfaces, VAMC-developed software, and HOST/COTS [[application~\|Application]]s.

	=== Consult/Request Tracking. ===		=== [[Consult/Request Tracking~\|Consult/Request Tracking]]. ===
	A fully functional consulting package is exported with [[CPRS~\|CPRS]]. Integrated tightly with [[CPRS~\|CPRS]], consults provides consult ordering/requesting, tracking, and resulting. Consulting events such as requesting and resulting trigger notifications to appropriate health care providers, who can then quickly react to the request or result.		A fully functional consulting package is exported with [[CPRS~\|CPRS]]. Integrated tightly with [[CPRS~\|CPRS]], consults provides consult ordering/requesting, tracking, and resulting. Consulting events such as requesting and resulting trigger notifications to appropriate health care providers, who can then quickly react to the request or result.

NeilArmstrong: Added a glossary link to CPRS~

2012-08-09T23:37:31Z

Added a glossary link to CPRS~

NeilArmstrong: Added a glossary link to Action~

2012-07-24T19:10:14Z

Added a glossary link to Action~

← Older revision		Revision as of 19:10, 24 July 2012
Line 49:		Line 49:

	=== Clinical Notifications. ===		=== Clinical Notifications. ===
	The Notifications component generates patient-specific clinical alerts regarding order entry, consult, radiology, lab, pharmacy, dietetics, and A/D/T information.Alerts are displayed to VISTA users when they sign onto the computer. They can also be delivered to printers, files, and terminals. Many alerts allow recipients to take related follow-up ~~actions~~. For example, a patient’s unsigned order triggers an alert to appropriate health care providers. When a recipient selects the alert, the follow-up action displays the patient’s unsigned orders and [[prompt~\|Prompt]]s for electronic signature. Via parameters, VAMCs can disable or enable notifications for users, teams, patient locations, services, divisions, and systems.		The Notifications component generates patient-specific clinical alerts regarding order entry, consult, radiology, lab, pharmacy, dietetics, and A/D/T information.Alerts are displayed to VISTA users when they sign onto the computer. They can also be delivered to printers, files, and terminals. Many alerts allow recipients to take related follow-up [[action~\|Action]]s. For example, a patient’s unsigned order triggers an alert to appropriate health care providers. When a recipient selects the alert, the follow-up [[action~\|Action]] displays the patient’s unsigned orders and [[prompt~\|Prompt]]s for electronic signature. Via parameters, VAMCs can disable or enable notifications for users, teams, patient locations, services, divisions, and systems.

	=== Order Checking. ===		=== Order Checking. ===

NeilArmstrong: Added glossary link to Record~

2012-03-14T14:45:20Z

Added glossary link to Record~

← Older revision		Revision as of 14:45, 14 March 2012
Line 1:		Line 1:
	= Overview of CPRS =		= Overview of CPRS =

	CPRS provides clinicians, managers, support staff, researchers, and others an integrated patient record system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, [[PCMM~\|PCMM]], [[PCE~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with CPRS. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and ~~records~~, as well as an efficient means for others to access and use patient information.		CPRS provides clinicians, managers, support staff, researchers, and others an integrated patient [[record~\|Record]]] system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, [[PCMM~\|PCMM]], [[PCE~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with CPRS. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and [[record~\|Record]]s, as well as an efficient means for others to access and use patient information.

	== Features: ==		== Features: ==

NeilArmstrong: Added glossary link to Prompt~

2012-03-05T10:54:01Z

Added glossary link to Prompt~

← Older revision		Revision as of 10:54, 5 March 2012
Line 49:		Line 49:

	=== Clinical Notifications. ===		=== Clinical Notifications. ===
	The Notifications component generates patient-specific clinical alerts regarding order entry, consult, radiology, lab, pharmacy, dietetics, and A/D/T information.Alerts are displayed to VISTA users when they sign onto the computer. They can also be delivered to printers, files, and terminals. Many alerts allow recipients to take related follow-up actions. For example, a patient’s unsigned order triggers an alert to appropriate health care providers. When a recipient selects the alert, the follow-up action displays the patient’s unsigned orders and ~~prompts~~ for electronic signature. Via parameters, VAMCs can disable or enable notifications for users, teams, patient locations, services, divisions, and systems.		The Notifications component generates patient-specific clinical alerts regarding order entry, consult, radiology, lab, pharmacy, dietetics, and A/D/T information.Alerts are displayed to VISTA users when they sign onto the computer. They can also be delivered to printers, files, and terminals. Many alerts allow recipients to take related follow-up actions. For example, a patient’s unsigned order triggers an alert to appropriate health care providers. When a recipient selects the alert, the follow-up action displays the patient’s unsigned orders and [[prompt~\|Prompt]]s for electronic signature. Via parameters, VAMCs can disable or enable notifications for users, teams, patient locations, services, divisions, and systems.

	=== Order Checking. ===		=== Order Checking. ===
	Order Checks are messages interactively displayed to the ordering provider during an ordering session. They occur in real-time and are driven by responses entered by the ordering provider in conjunction with existing patient data. Order Checks are rated according to potential clinical danger level. Order check messages with a low or moderate clinical danger level can be ignored. High clinical danger level order checks require the entry of a reason if they are overridden. This information is passed on to the filling package (e.g. pharmacy) as part of the order. All order check messages include a prompt to cancel or change the order. Via parameters, VAMCs can adjust order check clinical danger levels and disable or enable order checks for users, teams, patient locations, services, divisions, and systems.		Order Checks are messages interactively displayed to the ordering provider during an ordering session. They occur in real-time and are driven by responses entered by the ordering provider in conjunction with existing patient data. Order Checks are rated according to potential clinical danger level. Order check messages with a low or moderate clinical danger level can be ignored. High clinical danger level order checks require the entry of a reason if they are overridden. This information is passed on to the filling package (e.g. pharmacy) as part of the order. All order check messages include a [[prompt~\|Prompt]] to cancel or change the order. Via parameters, VAMCs can adjust order check clinical danger levels and disable or enable order checks for users, teams, patient locations, services, divisions, and systems.

	=== Online CPRS Demo ===		=== Online CPRS Demo ===

NeilArmstrong: Added glossary link to Application~

2012-02-22T14:44:19Z

Added glossary link to Application~

← Older revision		Revision as of 14:44, 22 February 2012
Line 31:		Line 31:

	=== HL7 Messaging/Event Processing. ===		=== HL7 Messaging/Event Processing. ===
	Communication between VISTA packages participating in CPRS is accomplished primarily through event-driven HL7 messaging. This approach allows multiple processes to subscribe to a single CPRS event. The structure and content of the HL7 message provides consistent data for processes subscribing to an event. Additional application programmer interfaces (APIs) exist between OE/RR and ancillary packages to provide data not supported by HL7.		Communication between VISTA packages participating in CPRS is accomplished primarily through event-driven HL7 messaging. This approach allows multiple processes to subscribe to a single CPRS event. The structure and content of the HL7 message provides consistent data for processes subscribing to an event. Additional [[application~\|Application]] programmer interfaces (APIs) exist between OE/RR and ancillary packages to provide data not supported by HL7.

	=== VAMC Parameters and Defaults. ===		=== VAMC Parameters and Defaults. ===
Line 37:		Line 37:

	=== Remote Procedure Calls. ===		=== Remote Procedure Calls. ===
	Generically written data extraction/storage remote procedure calls (RPCs) provide access to VISTA clinical data for CPRS interfaces, VAMC-developed software, and HOST/COTS ~~applications~~.		Generically written data extraction/storage remote procedure calls (RPCs) provide access to VISTA clinical data for CPRS interfaces, VAMC-developed software, and HOST/COTS [[application~\|Application]]s.

	=== Consult/Request Tracking. ===		=== Consult/Request Tracking. ===

NeilArmstrong: Added glossary link to Allergy~

2012-02-22T07:05:42Z

Added glossary link to Allergy~

← Older revision		Revision as of 07:05, 22 February 2012
Line 1:		Line 1:
	= Overview of CPRS =		= Overview of CPRS =

	CPRS provides clinicians, managers, support staff, researchers, and others an integrated patient record system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, Allergy Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, [[PCMM~\|PCMM]], [[PCE~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with CPRS. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and records, as well as an efficient means for others to access and use patient information.		CPRS provides clinicians, managers, support staff, researchers, and others an integrated patient record system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, [[PCMM~\|PCMM]], [[PCE~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with CPRS. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and records, as well as an efficient means for others to access and use patient information.

	== Features: ==		== Features: ==

NeilArmstrong: Added glossary link to Attending Physician~

2012-02-14T00:31:22Z

Added glossary link to Attending Physician~

← Older revision		Revision as of 00:31, 14 February 2012
Line 22:		Line 22:

	==== Patient selection. ====		==== Patient selection. ====
	Extensive patient selection capabilities allow physicians to build patient lists based on ward, room-bed, clinic appointment, patient’s primary provider/attending physician, team and individual patient. Once created, providers’ preferred patient lists are automatically loaded when they access CPRS. For example, a provider can set up a patient list based on each day’s clinic appointments. This list is built automatically each day and displayed to facilitate easier patient selection.		Extensive patient selection capabilities allow physicians to build patient lists based on ward, room-bed, clinic appointment, patient’s primary provider/[[attending physician~\|Attending Physician]], team and individual patient. Once created, providers’ preferred patient lists are automatically loaded when they access CPRS. For example, a provider can set up a patient list based on each day’s clinic appointments. This list is built automatically each day and displayed to facilitate easier patient selection.

	=== List Manager Interface. ===		=== List Manager Interface. ===

Anthracite at 18:13, 5 September 2011

2011-09-05T18:13:49Z

← Older revision		Revision as of 18:13, 5 September 2011
Line 57:		Line 57:

	You can quickly see a demo of CPRS by downloading the [http://www1.va.gov/cprsdemo/ VA CPRS Demo] from the VA.		You can quickly see a demo of CPRS by downloading the [http://www1.va.gov/cprsdemo/ VA CPRS Demo] from the VA.

			=== Adding Remote Procedures for Use with CPRS ===

			For CPRS RPCs, you must add them to the Option OR CPRS GUI CHART like this:

			GTM>D P^DI
			VA FileMan 22.0

			Select OPTION: 1 ENTER OR EDIT FILE ENTRIES

			INPUT TO WHAT FILE: OPTION
			1 OPTION (9906 entries)
			2 OPTION SCHEDULING (18 entries)
			CHOOSE 1-2: 1 OPTION (9906 entries)
			EDIT WHICH FIELD: ALL// RPC (multiple)
			EDIT WHICH RPC SUB-FIELD: ALL//
			THEN EDIT FIELD:

			Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.27.83
			Select RPC: ORWPT OTHER-RADIOBUTTONS// <=== ADD THE RPC NAME HERE

← Older revision		Revision as of 23:37, 9 August 2012
Line 1:		Line 1:
	= Overview of CPRS =		= Overview of [[CPRS~\|CPRS]] =

	CPRS provides clinicians, managers, support staff, researchers, and others an integrated patient [[record~\|Record]]] system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, [[PCMM~\|PCMM]], [[PCE~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with CPRS. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and [[record~\|Record]]s, as well as an efficient means for others to access and use patient information.		[[CPRS~\|CPRS]] provides clinicians, managers, support staff, researchers, and others an integrated patient [[record~\|Record]]] system. [[VISTA~\|VISTA]] software for [[Pharmacy~\|Pharmacy]], [[Laboratory~\|Lab]], Radiology, [[Allergy~\|Allergy]] Tracking, Consults, Dietetics, Progress Notes, Problem List, [[Scheduling~\|Scheduling]], MAS (A/D/T), Kernel, [[VA FileMan\|FileManager]], Vitals, [[PCMM~\|PCMM]], [[PCE~\|PCE]], [[TIU~\|TIU]], [[ASU~\|ASU]] and [[Clinical_Lexicon~\|Clinical Lexicon]] packages was written or modified to support and communicate with [[CPRS~\|CPRS]]. OE/RR was completely re-written. Together, these clinical components of VISTA provide a single interface for physicians to manage patient care and [[record~\|Record]]s, as well as an efficient means for others to access and use patient information.

	== Features: ==		== Features: ==

	=== Smooth transition from OE/RR ===		=== Smooth transition from OE/RR ===
	When a [[VAMC~\|VAMC]] installs CPRS, a fully automated process converts existing orders, order dialogs, orderable items, medications, labs, consults, clinical notifications and other components into CPRS. No patient data is lost and little or no manual conversion is required. Installation of CPRS only requires 1-2 hours of system downtime, with little impact on users and patient care. Because of its “user-friendly” design, most VA clinicians can use CPRS with minimal training.		When a [[VAMC~\|VAMC]] installs [[CPRS~\|CPRS]], a fully automated process converts existing orders, order dialogs, orderable items, medications, labs, consults, clinical notifications and other components into [[CPRS~\|CPRS]]. No patient data is lost and little or no manual conversion is required. Installation of [[CPRS~\|CPRS]] only requires 1-2 hours of system downtime, with little impact on users and patient care. Because of its “user-friendly” design, most VA clinicians can use [[CPRS~\|CPRS]] with minimal training.

	=== OE/RR core module. ===		=== OE/RR core module. ===
	All basic CPRS tasks occur within the M environment. Tasks relegated to the GUI workstation include those necessary to communicate with the server and to present and obtain data. Specific components of the core M module for OE/RR include:		All basic [[CPRS~\|CPRS]] tasks occur within the M environment. Tasks relegated to the GUI workstation include those necessary to communicate with the server and to present and obtain data. Specific components of the core M module for OE/RR include:
	==== Order processing and storage. ====		==== Order processing and storage. ====
	Processing orders in CPRS includes: 1) order dialog presentation, 2) order checking, 3) appropriate holding/processing/status assignment related to user credentials, order signature status, and filling package, 4) HL7 formatting, and 5) event posting for filling package and other interested parties, 6) receiving order status messages from filling package, and 7) updating the appropriate data files. Order storage in CPRS includes a complete, date/time-stamped history of all events related to the order including status changes, ordering, requesting, and signatory personnel, related order checks, and override reason, flagged order data, and various components related to the filling package.		Processing orders in [[CPRS~\|CPRS]] includes: 1) order dialog presentation, 2) order checking, 3) appropriate holding/processing/status assignment related to user credentials, order signature status, and filling package, 4) HL7 formatting, and 5) event posting for filling package and other interested parties, 6) receiving order status messages from filling package, and 7) updating the appropriate data files. Order storage in [[CPRS~\|CPRS]] includes a complete, date/time-stamped history of all events related to the order including status changes, ordering, requesting, and signatory personnel, related order checks, and override reason, flagged order data, and various components related to the filling package.
	==== Mechanism for clinical orderable items. ====		==== Mechanism for clinical orderable items. ====
	Orderable items are phrased in physician-friendly terms, centrally stored and can be updated at individual VAMCs. Updating is coordinated between OE/RR core and ancillary packages via HL7 messages.		Orderable items are phrased in physician-friendly terms, centrally stored and can be updated at individual VAMCs. Updating is coordinated between OE/RR core and ancillary packages via HL7 messages.
Line 22:		Line 22:

	==== Patient selection. ====		==== Patient selection. ====
	Extensive patient selection capabilities allow physicians to build patient lists based on ward, room-bed, clinic appointment, patient’s primary provider/[[attending physician~\|Attending Physician]], team and individual patient. Once created, providers’ preferred patient lists are automatically loaded when they access CPRS. For example, a provider can set up a patient list based on each day’s clinic appointments. This list is built automatically each day and displayed to facilitate easier patient selection.		Extensive patient selection capabilities allow physicians to build patient lists based on ward, room-bed, clinic appointment, patient’s primary provider/[[attending physician~\|Attending Physician]], team and individual patient. Once created, providers’ preferred patient lists are automatically loaded when they access [[CPRS~\|CPRS]]. For example, a provider can set up a patient list based on each day’s clinic appointments. This list is built automatically each day and displayed to facilitate easier patient selection.

	=== List Manager Interface. ===		=== List Manager Interface. ===
	Non-GUI, ANSI terminals use the CPRS List Manager interface. Designed with a great deal of clinician usability feedback, this interface displays allergies, lab results, medications, existing orders, consults, and other clinical data in a format conducive to decision making. The order entry process has been streamlined to gather the most pertinent information necessary to fill the order.		Non-GUI, ANSI terminals use the [[CPRS~\|CPRS]] List Manager interface. Designed with a great deal of clinician usability feedback, this interface displays allergies, lab results, medications, existing orders, consults, and other clinical data in a format conducive to decision making. The order entry process has been streamlined to gather the most pertinent information necessary to fill the order.

	=== GUI Interface. ===		=== GUI Interface. ===
	Clinical workstations in the Windows environment access CPRS through a Delphi-based Graphical User Interface (GUI). Based on years of prototyping, usability studies, and actual clinical use, the CPRS GUI is a full implementation of results reporting and order entry. It communicates with CPRS server processes through the Kernel Broker client-server utility. Data is exchanged via an extensive list of remote procedure calls.		Clinical workstations in the Windows environment access [[CPRS~\|CPRS]] through a Delphi-based Graphical User Interface (GUI). Based on years of prototyping, usability studies, and actual clinical use, the [[CPRS~\|CPRS]] GUI is a full implementation of results reporting and order entry. It communicates with [[CPRS~\|CPRS]] server processes through the Kernel Broker client-server utility. Data is exchanged via an extensive list of remote procedure calls.

	=== HL7 Messaging/Event Processing. ===		=== HL7 Messaging/Event Processing. ===
	Communication between VISTA packages participating in CPRS is accomplished primarily through event-driven HL7 messaging. This approach allows multiple processes to subscribe to a single CPRS event. The structure and content of the HL7 message provides consistent data for processes subscribing to an event. Additional [[application~\|Application]] programmer interfaces (APIs) exist between OE/RR and ancillary packages to provide data not supported by HL7.		Communication between VISTA packages participating in [[CPRS~\|CPRS]] is accomplished primarily through event-driven HL7 messaging. This approach allows multiple processes to subscribe to a single [[CPRS~\|CPRS]] event. The structure and content of the HL7 message provides consistent data for processes subscribing to an event. Additional [[application~\|Application]] programmer interfaces (APIs) exist between OE/RR and ancillary packages to provide data not supported by HL7.

	=== VAMC Parameters and Defaults. ===		=== VAMC Parameters and Defaults. ===
	Every VAMC has specialized needs regarding CPRS functionality and processing. To allow variation and modification among VAMCs, CPRS provides a hierarchically structured set of parameters. Each parameter can have a user, team, service/section, patient location, division, system, and package value. The extensive set of parameters exported with CPRS allows VAMC administrators and CPRS users to fine-tune the functionalities and processes specific to their needs.		Every VAMC has specialized needs regarding [[CPRS~\|CPRS]] functionality and processing. To allow variation and modification among VAMCs, [[CPRS~\|CPRS]] provides a hierarchically structured set of parameters. Each parameter can have a user, team, service/section, patient location, division, system, and package value. The extensive set of parameters exported with [[CPRS~\|CPRS]] allows VAMC administrators and [[CPRS~\|CPRS]] users to fine-tune the functionalities and processes specific to their needs.

	=== Remote Procedure Calls. ===		=== Remote Procedure Calls. ===
	Generically written data extraction/storage remote procedure calls (RPCs) provide access to VISTA clinical data for CPRS interfaces, VAMC-developed software, and HOST/COTS [[application~\|Application]]s.		Generically written data extraction/storage remote procedure calls (RPCs) provide access to VISTA clinical data for [[CPRS~\|CPRS]] interfaces, VAMC-developed software, and HOST/COTS [[application~\|Application]]s.

	=== Consult/Request Tracking. ===		=== Consult/Request Tracking. ===
	A fully functional consulting package is exported with CPRS. Integrated tightly with CPRS, consults provides consult ordering/requesting, tracking, and resulting. Consulting events such as requesting and resulting trigger notifications to appropriate health care providers, who can then quickly react to the request or result.		A fully functional consulting package is exported with [[CPRS~\|CPRS]]. Integrated tightly with [[CPRS~\|CPRS]], consults provides consult ordering/requesting, tracking, and resulting. Consulting events such as requesting and resulting trigger notifications to appropriate health care providers, who can then quickly react to the request or result.

	=== Patient/Team Lists. ===		=== Patient/Team Lists. ===
	Patient and Team List functionality in CPRS provides several methods for linking health care providers with patients. Team relationships can be based on ward, room-bed, provider, specialty, and/or clinic. Membership is updated automatically when patients are admitted, discharged, transferred, or assigned to a clinic.		Patient and Team List functionality in [[CPRS~\|CPRS]] provides several methods for linking health care providers with patients. Team relationships can be based on ward, room-bed, provider, specialty, and/or clinic. Membership is updated automatically when patients are admitted, discharged, transferred, or assigned to a clinic.

	=== Expert System. ===		=== Expert System. ===
	The CPRS Expert System is a modular, rule-oriented, knowledge-based system. It supports CPRS as the basis for real-time order checking (e.g. critical drug interactions, duplicate orders) and background notifications (e.g. critical lab results, expiring medications.) Components include: a Meta-Dictionary for linking discrete medical concepts with data located in files, messages and dialogs; a Rule Editor for creating and editing medical logic modules (MLMs) or rules which relate meta-dictionary concepts in logical expressions; an Inferencing Engine for processing the rules against data; and a Router for distributing results or messages.		The [[CPRS~\|CPRS]] Expert System is a modular, rule-oriented, knowledge-based system. It supports [[CPRS~\|CPRS]] as the basis for real-time order checking (e.g. critical drug interactions, duplicate orders) and background notifications (e.g. critical lab results, expiring medications.) Components include: a Meta-Dictionary for linking discrete medical concepts with data located in files, messages and dialogs; a Rule Editor for creating and editing medical logic modules (MLMs) or rules which relate meta-dictionary concepts in logical expressions; an Inferencing Engine for processing the rules against data; and a Router for distributing results or messages.

	=== Clinical Notifications. ===		=== Clinical Notifications. ===
Line 54:		Line 54:
	Order Checks are messages interactively displayed to the ordering provider during an ordering session. They occur in real-time and are driven by responses entered by the ordering provider in conjunction with existing patient data. Order Checks are rated according to potential clinical danger level. Order check messages with a low or moderate clinical danger level can be ignored. High clinical danger level order checks require the entry of a reason if they are overridden. This information is passed on to the filling package (e.g. pharmacy) as part of the order. All order check messages include a [[prompt~\|Prompt]] to cancel or change the order. Via parameters, VAMCs can adjust order check clinical danger levels and disable or enable order checks for users, teams, patient locations, services, divisions, and systems.		Order Checks are messages interactively displayed to the ordering provider during an ordering session. They occur in real-time and are driven by responses entered by the ordering provider in conjunction with existing patient data. Order Checks are rated according to potential clinical danger level. Order check messages with a low or moderate clinical danger level can be ignored. High clinical danger level order checks require the entry of a reason if they are overridden. This information is passed on to the filling package (e.g. pharmacy) as part of the order. All order check messages include a [[prompt~\|Prompt]] to cancel or change the order. Via parameters, VAMCs can adjust order check clinical danger levels and disable or enable order checks for users, teams, patient locations, services, divisions, and systems.

	=== Online CPRS Demo ===		=== Online [[CPRS~\|CPRS]] Demo ===

	You can quickly see a demo of CPRS by downloading the [http://www1.va.gov/cprsdemo/ VA CPRS Demo] from the VA.		You can quickly see a demo of [[CPRS~\|CPRS]] by downloading the [http://www1.va.gov/cprsdemo/ VA CPRS Demo] from the VA.

	=== Adding Remote Procedures for Use with CPRS ===		=== Adding Remote Procedures for Use with [[CPRS~\|CPRS]] ===

	For CPRS RPCs, you must add them to the Option OR CPRS GUI CHART like this:		For [[CPRS~\|CPRS]] RPCs, you must add them to the Option OR [[CPRS~\|CPRS]] GUI CHART like this:

	GTM>D P^DI		GTM>D P^DI
Line 75:		Line 75:
	THEN EDIT FIELD:		THEN EDIT FIELD:

	Select OPTION NAME: OR CPRS GUI CHART ~~CPRSChart~~ version 1.0.27.83		Select OPTION NAME: OR [[CPRS\|CPRS]] GUI CHART [[CPRS~\|CPRS]]Chart version 1.0.27.83
	Select RPC: ORWPT OTHER-RADIOBUTTONS// <=== ADD THE RPC NAME HERE		Select RPC: ORWPT OTHER-RADIOBUTTONS// <=== ADD THE RPC NAME HERE