Retrieve Protocol for Execution: Difference between revisions
Jump to navigation
Jump to search
Dwhittenburg (talk | contribs) |
Dwhittenburg (talk | contribs) No edit summary |
||
| Line 58: | Line 58: | ||
;Submit Regulatory Documentation | ;Submit Regulatory Documentation | ||
;Enroll Patient | ;Enroll Patient | ||
=Volume II= | =Volume II= | ||
Revision as of 13:55, 22 December 2008
Introduction
This is a draft of the Retrieve Protocol for Execution Profile (RPE) from the QRPH Domain.
Meeting Minutes
- 12/12 - Discussed Detailed Proposal
- 12/19 - Discussed RPE Use Case Graphic
Profile Abstract
Add a profile abstract on this page. For now going to continue to show link to detail proposal
- Retrieve Protocol for Execution Detailed Proposal
Issue Log
Open Issues
Closed Issues
Volume I
Dependencies
Overview
Scope
Example
Use Case
In the uses cases below, we describe the before and after effects of implementing the Retrieve Protocol for Execution profile. for now in Detailed Proposal
Before Care Management
- Preconditions
- Use Case
- Postconditions
After Care Management
- Precondition
- Use Case
- Postcondition
Actors/Transaction
Process/Flow
Actor Definitions
- Protocol Executor
- receives the protocol instruction and executes it
- Protocol Manager
- manages a collection of protocols
Transaction Definitions
- Publish Protocol
- Retrieve Protocol List
- Enroll in Protocol
- Retreive Protocol
- Submit Protocol Documentation (maybe use Enroll in Protocol)
- Submit Approval
- Retrieve Approval
- Submit Regulatory Documentation
- Enroll Patient
Volume II
Retrieve Protocol for Execution Content
Standards
Interaction Diagrams
Resources
Return to Quality, Research and Public Health Domain Main Page
Return to Quality, Research and Public Health Planning Committee
Return to Quality, Research and Public Health Technical Committee