Card Tech Minutes 2016.02.10: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
:XDS Use | :'''XDS Use Case Discussion''' | ||
:* Elena has clarified the description between the system and users. Use Case 1 breaks down the roles between the Heart Team {HT} Requester, Heart Team Manager, and the Heart Team Participants. This should allow for the | :* Use Case 1 - Simple: Elena has clarified the description between the system and users. Use Case 1 breaks down the roles between the Heart Team {HT} Requester, Heart Team Manager, and the Heart Team Participants. This should allow for the HT Manager, likely to be the cardiac surgeon being consulted. | ||
: | :* ''The HT Manager schedule teleconference'' could be too specific for most situations. A simple phone call may be able to communicate results and plan for further interventions with the referring clinicians. Perhaps labeling it as an ''interaction'' or ''communication point'' could save time with a simple phone call, or a web conference if needed to allow for flexibility between providers. | ||
:*What occasions are there for pre-approval for tests? How could the workflow handle requests for exams that won't be performed, possibly because they had occurred and the results were not communicated. | |||
:* Use Case 2 - Complex: Adding more participants to workflow including other communication loops and document sharing between HT members. | |||
:*Elena found a flow chart error that will be resolved in subsequent drafts. | |||
:* The use cases also include discussion for handling cancelation requests. The workflows may need exit points for critical results from testing results. In the real world setting there may be other unexpected situations that occur. An ''In Case of Emergency Break Glass'' point that requires an accelerated workflow. For example it can move directly to emergency surgery, or some similar result. The question then becomes, what do we do when the process is bypassed? How do we return to the workflow once we have ejected from the process? This may need to be discussed at a higher level, perhaps similar to how the process is handled in other XDW workflows. | |||
Latest revision as of 10:54, 10 February 2016
- XDS Use Case Discussion
- Use Case 1 - Simple: Elena has clarified the description between the system and users. Use Case 1 breaks down the roles between the Heart Team {HT} Requester, Heart Team Manager, and the Heart Team Participants. This should allow for the HT Manager, likely to be the cardiac surgeon being consulted.
- The HT Manager schedule teleconference could be too specific for most situations. A simple phone call may be able to communicate results and plan for further interventions with the referring clinicians. Perhaps labeling it as an interaction or communication point could save time with a simple phone call, or a web conference if needed to allow for flexibility between providers.
- What occasions are there for pre-approval for tests? How could the workflow handle requests for exams that won't be performed, possibly because they had occurred and the results were not communicated.
- Use Case 2 - Complex: Adding more participants to workflow including other communication loops and document sharing between HT members.
- Elena found a flow chart error that will be resolved in subsequent drafts.
- The use cases also include discussion for handling cancelation requests. The workflows may need exit points for critical results from testing results. In the real world setting there may be other unexpected situations that occur. An In Case of Emergency Break Glass point that requires an accelerated workflow. For example it can move directly to emergency surgery, or some similar result. The question then becomes, what do we do when the process is bypassed? How do we return to the workflow once we have ejected from the process? This may need to be discussed at a higher level, perhaps similar to how the process is handled in other XDW workflows.