Card Tech Minutes 2016.11.09: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
''CRC and CIRC Harmonizing'' | ''CRC and CIRC Harmonizing'' | ||
:An off line discussion led to the conclusion that we could bring the CIRC profile, into CRC and possibly EPRC-IE to create one larger profile that covers the entirety of reporting. The benefit is that this brings three profiles into one streamlined procedure noting profile that folds into the framework. | :An off line discussion led to the conclusion that we could bring the CIRC profile, into CRC and possibly EPRC-IE to create one larger profile that covers the entirety of reporting. The benefit is that this brings three profiles into one streamlined procedure noting profile that folds into the framework. | ||
*1. Update CRC to CCDA ver 2.1 | *1. Update CRC to CCDA ver 2.1. This would begin with the version that include the Structural Heart Interventions work that was recently published. It would also include addressing some issues raised during implementation experience. | ||
*2. Harmonize with EPRC-IE to leverage the learnings and enhancements for support for EP procedures. There were some changes made to the templates to address specific EP needs. We should be able to fold these back in to create a common set of templates for both CRC and EP. | |||
*3. | *3. Include support for diagnostic imaging exams that is currently in CIRC profile. This would result in using the common templates for these exams as well but would eliminate the need for the separate CIRC profile. There would be options defined for the specific document types - e.g. diagnostic, cath, EP, etc. | ||
:This will include non-invasive imaging like echo in the CIRC profile. This profile will not replace the registry content submission reports. The complexity of pulling the information from the templates does require extra effort. ''Q: We'll need to ask Dino about clarifying the complexity: is it pulling the procedure report into the CDA or pulling the CDA into the Registry?'' | :This will include non-invasive imaging like echo in the CIRC profile. This profile will not replace the registry content submission reports. The complexity of pulling the information from the templates does require extra effort. ''Q: We'll need to ask Dino about clarifying the complexity: is it pulling the procedure report into the CDA or pulling the CDA into the Registry?'' | ||
Revision as of 11:15, 9 November 2016
Attendees
- Chris Melo, Philips, Co-chair
- Nick Gawrit, Heartbase, Co-chair
- Paul Dow, ACC, Secretary
- Antje Schroeder, Siemens
- Rebecca Baker, ACC
- Charles Thomas, University of Washington
- Dan Murphy, Epic
- Jerry Serwer, University of Michigan, PC Co-Chair
- Andrea Price, Indiana University
- Denise Downing, AORN, 'PCC Domain Co-Chair
Minutes
CRC and CIRC Harmonizing
- An off line discussion led to the conclusion that we could bring the CIRC profile, into CRC and possibly EPRC-IE to create one larger profile that covers the entirety of reporting. The benefit is that this brings three profiles into one streamlined procedure noting profile that folds into the framework.
- 1. Update CRC to CCDA ver 2.1. This would begin with the version that include the Structural Heart Interventions work that was recently published. It would also include addressing some issues raised during implementation experience.
- 2. Harmonize with EPRC-IE to leverage the learnings and enhancements for support for EP procedures. There were some changes made to the templates to address specific EP needs. We should be able to fold these back in to create a common set of templates for both CRC and EP.
- 3. Include support for diagnostic imaging exams that is currently in CIRC profile. This would result in using the common templates for these exams as well but would eliminate the need for the separate CIRC profile. There would be options defined for the specific document types - e.g. diagnostic, cath, EP, etc.
- This will include non-invasive imaging like echo in the CIRC profile. This profile will not replace the registry content submission reports. The complexity of pulling the information from the templates does require extra effort. Q: We'll need to ask Dino about clarifying the complexity: is it pulling the procedure report into the CDA or pulling the CDA into the Registry?
Denise Downing {AORN} and PCC Co-chair and UDI
- Implantable Medical Device Registry Profile and possible collaboration between PCC and Card Domains. This profile could be useful for a wide range of devices. these would include the measurements from devices, which is very important to Cardiology. This may also offer surveillance. This will be a FHIR based profile that specifics the pt, devices and operator. There will be a new actor developed, "Point-of-Care Device Manager