Difference between revisions of "Retrieve Process for Execution"
| Line 1: | Line 1: | ||
| − | |||
| − | |||
__TOC__ | __TOC__ | ||
==Summary== | ==Summary== | ||
| − | + | Retrieve Process for Execution (RPE) enables a healthcare provider to access a process definition, such as a research protocol, and to execute automated activities, without leaving an EHR session. | |
| + | |||
RPE is one of a set of profiles that create interoperability between EHRs and specialized research systems, resulting in EHR-enabled research. RPE sets up the actors and transactions that allow for automated collaborative workflow across healthcare and research systems. | RPE is one of a set of profiles that create interoperability between EHRs and specialized research systems, resulting in EHR-enabled research. RPE sets up the actors and transactions that allow for automated collaborative workflow across healthcare and research systems. | ||
| − | + | ||
| + | Current practice requires the study coordinator to manually reference the protocol to set up the study in the EHR. RPE and its content profiles allow this set up to be automated, thus saving time in the execution of studies. | ||
==Benefits== | ==Benefits== | ||
| − | + | RPE provides the framework for automating workflow across EHRs and research execution systems. The execution of a research study at a healthcare site involves the access of relevant data, the province of RFD, CRD, and DSC. But research study execution also involves process steps that go beyond data acquisition. Tasks such as patient enrollment, visit scheduling, and ordering tests require that certain instructions of the protocol be executed by the EHR. | |
| − | RPE provides the framework for automating workflow across EHRs and research execution systems. The execution of a research study at a healthcare site involves the access of relevant data, the province of RFD, CRD, and DSC. But research study execution also involves process steps that go beyond data acquisition. Tasks such as patient enrollment, visit scheduling, and ordering tests require that certain instructions of the protocol be executed by the EHR. | ||
| − | |||
| − | |||
| − | |||
| − | |||
==Details== | ==Details== | ||
| − | + | ||
The RPE profile sets up actors which hold sections of the research protocol as executable instruction sets. The Process Definition Manager holds the master copy of protocol. The Process State Manager hands off the executable instructions to the Process Activity Executor, which abides in the EHR. | The RPE profile sets up actors which hold sections of the research protocol as executable instruction sets. The Process Definition Manager holds the master copy of protocol. The Process State Manager hands off the executable instructions to the Process Activity Executor, which abides in the EHR. | ||
| − | + | ||
| − | |||
RPE defines transactions that allow these actors to do useful work together. These transactions can then be extended and specialized by content profiles such as CRPC and Research Matching. RPE transactions are: | RPE defines transactions that allow these actors to do useful work together. These transactions can then be extended and specialized by content profiles such as CRPC and Research Matching. RPE transactions are: | ||
| − | + | * Retrieve Process Definitions (QRPH-20) | |
| − | + | * Publish Process Definitions (QRPH-22) | |
| − | + | * Initiate Process (QRPH-25) | |
| − | + | * Retrieve Activities (QRPH-26) | |
| − | + | * Update Activity (QRPH-27) | |
| − | + | * Send Process State Alert (QRPH-28) | |
| − | |||
| + | |||
==Systems Affected== | ==Systems Affected== | ||
| − | + | * Electronic Health Record | |
| − | + | * Research Protocol System | |
| − | + | ||
| − | |||
==Specification== | ==Specification== | ||
| − | + | Profile Status: [[Comments| Trial Implementation]] | |
| − | + | Documents: | |
| + | * [[http://ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_RPE.pdf Retrieve Process for Execution (RPE) ]] | ||
| − | |||
| − | + | ==See Also== | |
| + | |||
| + | Related Profiles | ||
| + | * [[http://ihe.net/uploadedFiles/Documents/QRPH/IHE_QRPH_Suppl_CRPC.pdf Clinical Research Process Content (CRPC) ]] | ||
| − | |||
| − | |||
| − | |||
[[Category:Profiles]] | [[Category:Profiles]] | ||
[[Category:QRPH Profile]] | [[Category:QRPH Profile]] | ||
| + | |||
| + | This page is based on the [[Profile Overview Template]] | ||
Revision as of 10:35, 20 April 2018
Summary
Retrieve Process for Execution (RPE) enables a healthcare provider to access a process definition, such as a research protocol, and to execute automated activities, without leaving an EHR session.
RPE is one of a set of profiles that create interoperability between EHRs and specialized research systems, resulting in EHR-enabled research. RPE sets up the actors and transactions that allow for automated collaborative workflow across healthcare and research systems.
Current practice requires the study coordinator to manually reference the protocol to set up the study in the EHR. RPE and its content profiles allow this set up to be automated, thus saving time in the execution of studies.
Benefits
RPE provides the framework for automating workflow across EHRs and research execution systems. The execution of a research study at a healthcare site involves the access of relevant data, the province of RFD, CRD, and DSC. But research study execution also involves process steps that go beyond data acquisition. Tasks such as patient enrollment, visit scheduling, and ordering tests require that certain instructions of the protocol be executed by the EHR.
Details
The RPE profile sets up actors which hold sections of the research protocol as executable instruction sets. The Process Definition Manager holds the master copy of protocol. The Process State Manager hands off the executable instructions to the Process Activity Executor, which abides in the EHR.
RPE defines transactions that allow these actors to do useful work together. These transactions can then be extended and specialized by content profiles such as CRPC and Research Matching. RPE transactions are:
- Retrieve Process Definitions (QRPH-20)
- Publish Process Definitions (QRPH-22)
- Initiate Process (QRPH-25)
- Retrieve Activities (QRPH-26)
- Update Activity (QRPH-27)
- Send Process State Alert (QRPH-28)
Systems Affected
- Electronic Health Record
- Research Protocol System
Specification
Profile Status: Trial Implementation
Documents:
See Also
Related Profiles
This page is based on the Profile Overview Template