Card Tech Minutes 2015.11.09-11: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
==='''November 10th, Tuesday, Conf Room 112'''=== | ==='''November 10th, Tuesday, Conf Room 112'''=== | ||
:*'''EP White Paper Review:''' Discussion of the Buxton Report and the review of a PPT that highlighted the benefits of a standardized workflow.The goal is to have this completed by Feb 15, 2016 for David Slotwiner to present at the HRS annual meeting. The HPS for ICD/Ablation should be published by May 4, 2016. | :*'''EP White Paper Review:''' Discussion of the Buxton Report and the review of a PPT that highlighted the benefits of a standardized workflow.The goal is to have this completed by Feb 15, 2016 for David Slotwiner to present at the HRS annual meeting. The HPS for ICD/Ablation should be published by May 4, 2016. | ||
:* Planning | :* '''Cycle Planning:''' Refinement of the cycle project times lines for RCS-C and RCS-EP. These will be updated and posted here. | ||
:* '''Cardiovascular Consult:''' Arsenal IT presents details around the Cardiology Consult profile. This may be developed with the assistance of the PCC Domain. The discussion included the development of uses cases in acute and sub-acute settings. The first was a simple case with limited IT. The second was more clinically complex with extensive IT support. An emphasis on XDS/DSUB/XDW infrastructure brings flexibility to exchanging clinical information. There will be continuing conversations through the week with the Tech Committee and the Planning Committee on Thursday. Tomorrow will include a draft of Volume One: Uses Cases, Actors, etc. Members of the PCC Domain were invited to participate. ''Questions: Are all of the use cases covered? Are there possible deviations that could lead the workflow down other unintended pathways? What are some other decision points around patient transfers that could impact the workflow and profile complexity?'' | :* '''Cardiovascular Consult:''' Arsenal IT presents details around the Cardiology Consult profile. This may be developed with the assistance of the PCC Domain. The discussion included the development of uses cases in acute and sub-acute settings. The first was a simple case with limited IT. The second was more clinically complex with extensive IT support. An emphasis on XDS/DSUB/XDW infrastructure brings flexibility to exchanging clinical information. There will be continuing conversations through the week with the Tech Committee and the Planning Committee on Thursday. Tomorrow will include a draft of Volume One: Uses Cases, Actors, etc. Members of the PCC Domain were invited to participate. ''Questions: Are all of the use cases covered? Are there possible deviations that could lead the workflow down other unintended pathways? What are some other decision points around patient transfers that could impact the workflow and profile complexity?'' | ||
:* '''RCS-C v5.0 Updates:''' Review of the changes and harmonization with RCS-EP. | :* '''RCS-C v5.0 Updates:''' Review of the changes and steps to improve harmonization with RCS-EP. Discussion of the vocabulary constraints with regards to patient demographics. | ||
Revision as of 13:19, 10 November 2015
November 9th, Monday, Conf Room 114
- Tech Framework Maintenance: Discussion of the CP for the
November 10th, Tuesday, Conf Room 112
- EP White Paper Review: Discussion of the Buxton Report and the review of a PPT that highlighted the benefits of a standardized workflow.The goal is to have this completed by Feb 15, 2016 for David Slotwiner to present at the HRS annual meeting. The HPS for ICD/Ablation should be published by May 4, 2016.
- Cycle Planning: Refinement of the cycle project times lines for RCS-C and RCS-EP. These will be updated and posted here.
- Cardiovascular Consult: Arsenal IT presents details around the Cardiology Consult profile. This may be developed with the assistance of the PCC Domain. The discussion included the development of uses cases in acute and sub-acute settings. The first was a simple case with limited IT. The second was more clinically complex with extensive IT support. An emphasis on XDS/DSUB/XDW infrastructure brings flexibility to exchanging clinical information. There will be continuing conversations through the week with the Tech Committee and the Planning Committee on Thursday. Tomorrow will include a draft of Volume One: Uses Cases, Actors, etc. Members of the PCC Domain were invited to participate. Questions: Are all of the use cases covered? Are there possible deviations that could lead the workflow down other unintended pathways? What are some other decision points around patient transfers that could impact the workflow and profile complexity?
- RCS-C v5.0 Updates: Review of the changes and steps to improve harmonization with RCS-EP. Discussion of the vocabulary constraints with regards to patient demographics.