|
|
| Line 1: |
Line 1: |
| Retrieve Process for Execution enables a healthcare provider to access a process definition, such as a research protocol and to execute automated activities, without leaving an EMR session. | | 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. |
|
| |
|
| __TOC__ | | __TOC__ |
|
| |
|
| ==Summary== | | ==Summary== |
| ''<Describe the profile in about a paragraph using user-oriented language. Focus on what it accomplishes for a user (i.e. the Use Cases). Don't get into how it works, leave that to the Details section.>''
| | <p> |
| | | 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. |
| ''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>''
| | </p> |
| | |
| ''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
| |
|
| |
|
| ==Benefits== | | ==Benefits== |
| ''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile. If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
| | <p> |
| | 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. |
| | </p> |
| | <p> |
| | 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. |
| | </p> |
|
| |
|
| ==Details== | | ==Details== |
| | <p> |
| | 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. |
| | </p> |
| | <p> |
| | 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: |
| | <ul> |
| | <li> Retrieve process definitions |
| | <li> Initiate process |
| | <li> Retrieve activities |
| | <li> Update activities |
| | </ul> |
| | </p> |
|
| |
|
| ''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
| |
|
| |
| ''<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
| |
|
| |
| ''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
| |
|
| |
| ==Systems Affected== | | ==Systems Affected== |
| ''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
| | <ul> |
| | | <li> Electronic Health Record |
| * ''PACS systems may store, manage, and/or display Evidence Documents.''
| | <li> Research Protocol System |
| * ''Display systems may query, retrieve and display Evidence Documents.''
| | </ul> |
| * ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
| |
| | |
| '''Actors & Transactions:'''
| |
| | |
| ''<Insert an actor-transaction diagram, and or list of Content Definitions>''
| |
|
| |
|
| ==Specification== | | ==Specification== |
|
| |
|
| '''Profile Status:''' [[Comments| Final Text]] | | '''Profile Status:''' [[Comments| Trial Implementation]] |
| ''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
| |
|
| |
|
| '''Documents:''' | | '''Documents:''' |
|
| |
|
| ''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>'' | | ''http://ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_RPE_Rev3-1_TI_2011-09-02.pdf'' |
| | |
| [http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
| |
| :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
| |
| :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
| |
| :* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
| |
| | |
| '''Underlying Standards:'''
| |
| | |
| ''<list all the standards on which the profile is based; if possible with links to sources>''
| |
| :* [http://dicom.nema.org DICOM]
| |
| :* [http://www.hl7.org HL7]
| |
| :* ...
| |
| | |
| ==See Also==
| |
| | |
| ''<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>''
| |
| | |
| | |
| '''Related Profiles'''
| |
| | |
| ''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>''
| |
| | |
| * ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
| |
| * ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
| |
| * ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
| |
| * ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
| |
| * ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
| |
| | |
| | |
| '''Consumer Information'''
| |
| | |
| The [[Profile FAQ Template]] answers typical questions about what the Profile does. ''<Replace the link with a link to the actual FAQ page for the Profile>''
| |
| | |
| The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile. ''<Replace the link with a link to the actual Purchasing page for the Profile>''
| |
| | |
| '''Implementer Information'''
| |
| | |
| The [[Profile Implementation Template]] provides additional information about implementing this Profile in software. ''<Replace the link with a link to the actual Implementation page for the Profile>''
| |
| | |
| '''Reference Articles'''
| |
| | |
| ''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >''
| |
| | |
|
| |
|
| | ''' Supporting Standards: ''' |
|
| |
|
| This page is based on the [[Profile Overview Template]]
| | <ul> |
| | <li> BPMN 2.0 |
| | </ul> |
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.
Summary
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.
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.
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.
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
- Initiate process
- Retrieve activities
- Update activities
Systems Affected
- Electronic Health Record
- Research Protocol System
Specification
Profile Status: Trial Implementation
Documents:
http://ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_RPE_Rev3-1_TI_2011-09-02.pdf
Supporting Standards: