Card Tech Minutes 2011.04.27: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Line 32: Line 32:
# Whitepaper udate
# Whitepaper udate
#* The EP whitepaper is about 80% done, three major use cases have been flashed out  
#* The EP whitepaper is about 80% done, three major use cases have been flashed out  
#**Physician user captures the report from an EP ICD implant procedure and produces a CDA document that becomes the basic CDA document containing data related to the procedure.
#**Nurse enters data in NCDR ICD Registry form with some of the data pre-populated by the basic CDA document containing data related to ICD implant procedure.
#**Hospital submits data to NCDR ICD Registry form with some of the data pre-populated.
#* Version 2 of the document can be found at [ftp://ftp.ihe.net/Cardio/Year6-2010-2012/Technical_Cmte/TF_Supplement_Development/EPKeyDataElementswhitepaper/]
#* Version 2 of the document can be found at [ftp://ftp.ihe.net/Cardio/Year6-2010-2012/Technical_Cmte/TF_Supplement_Development/EPKeyDataElementswhitepaper/]


# Scheduling
# Scheduling

Revision as of 06:03, 28 April 2011

Attendees

  • Tom Dolan - Philips
  • Bryan Jennings - Medical Micrographics
  • Nick Gawritt - Heartbase
  • Dan Roman - ACC
  • Mary Schneider -GE
  • Antje Schroeder - Siemens
  • Harry Solomon - GE
  • Paul Seifert - Agfa


Minutes

  1. TF Maintenance
    • Connectathon Project Management publishes all relevant documents for the 2012 North American Connectathon on Aug. 22, 2011 on the connectathon wiki => updated TF and supplements have to be published by then.
    • CP review
      • CP001: Add PCC relevant content. No text yet, not relevant for connectathon testing
      • CP007: Clarifications regarding SOP Classes supported in Echo and Cath Evidence Documents for Image Manager/Archives in Card-2. Paul proposed two solutions:
        • Add options for Echo and Cath Evidence (similiar to how it is done in ECHO and CATH profiles) and reference tables with SOP Classes within option text
        • Following the approach taken in REWF and add new subsections describing
      • CP008: Clarifications for STRESS supplement. Upon initial review of the CP, it was not clear what changes are required. Harry will investigate
      • CP010: HL7 Profiling conventions. Profiling convention section will be replaced by a reference to ITI Volume 2.x. Ready for ballot
      • CP011: Clarification on Actor Grouping in REWF. Ready for ballot
    • The Technical Committee will vote whether to submit the CPs for ballot during the May 11 meeting. Quorum is needed, therefore please attend meeting. Goal is to publish the updated supplements and TF documents on July 20. Details on the schedule see below.
  2. CIRC
    • CIRC was published for public comment on April 26. Public comments will be addressed during the F2F meeting in Washington May 24-25. The plan is to publish for trial implementation by June 20.
    • Nick agreed to support Harry in modeling the findings section
    • Harry will reach out to the PCC domain for comments during their F2F meeting next week. Also ask for review in Domain Coordination Committee call.
  3. IHE Activities at ESC show
    • Cocir is soliciting interest in an interoperability demo at the ESC show in Aug. 2011. They are planning on an exhibit area for home monitoring.
    • Harry will follow up with Nicole Denjoy (Cocir)and Ennel Vanderbilt (Computers in Cardiology work group of ESC) as to what the status of an interoperability demo is.
  4. Whitepaper udate
    • The EP whitepaper is about 80% done, three major use cases have been flashed out
      • Physician user captures the report from an EP ICD implant procedure and produces a CDA document that becomes the basic CDA document containing data related to the procedure.
      • Nurse enters data in NCDR ICD Registry form with some of the data pre-populated by the basic CDA document containing data related to ICD implant procedure.
      • Hospital submits data to NCDR ICD Registry form with some of the data pre-populated.
    • Version 2 of the document can be found at [1]
  1. Scheduling