Difference between revisions of "SSDMeeting2008 02 04"

From HL7 TSC
Jump to navigation Jump to search
(New page: <p><center><big><b>SSD Steering Group</b></big></center></p> <center><small>Minutes of Feb 04, 2008</small></center> <p></p> <table> <tr><th width=15%>Name</th><th width=37%>Organization</...)
 
 
(2 intermediate revisions by the same user not shown)
Line 15: Line 15:
 
</table>
 
</table>
 
<p></p>
 
<p></p>
 +
 +
==== Agenda &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Item Description ====
 +
=====&nbsp;&nbsp;&nbsp;&nbsp;Item 1: [http://www.hl7.org/library/committees/sigvi/CCOW%20SAML%20Project%20Scope%20Statement%20%28CCOW-SAML%29%202008FEB04.doc CCOW SAML Project Scope Statement]=====
 +
 +
=====&nbsp;&nbsp;&nbsp;&nbsp;Item 2: [http://www.hl7.org/Library/Committees/structure/HL7SDTC%20QRDA%20Project%20Scope%20Statement.Jan16081.SDTC.doc QRDA Project Scope Statement]=====
 +
 +
=====&nbsp;&nbsp;&nbsp;&nbsp;Item 3: [http://www.hl7.org/Library/Committees/structure/HL7%20SD%20TC%20P-toP%20PHR%20Data%20Transfer%20Project%20Scope%20Statement%20draft%20ver1%2001_23_2008.doc P-to-P PHR Data Transfer Project Scope]=====
 +
 +
=====&nbsp;&nbsp;&nbsp;&nbsp;Item 4: [http://www.hl7.org/Library/Committees/structure/HL7%20Project%20Scope%20Statement%20PHM3.Continua.doc Continua Project Scope Statement]=====
 +
 +
=====&nbsp;&nbsp;&nbsp;&nbsp;Item 5: [http://www.hl7.org/library/committees/ehr/HL7%20EHR%20VR%20Profile%20Project%20Scope%20Statement%20draft%2020080123%20ver2.doc EHR VR Profile Scope Statement]=====
 +
 +
=====&nbsp;&nbsp;&nbsp;&nbsp;Item 6: Quorum Rules=====
 +
  
 
====Project proposal was presented for the SAML support====
 
====Project proposal was presented for the SAML support====
Line 25: Line 39:
 
The objective is to produce a normative update to the current CCOW specification that will describe the use of SAML within the CCOW architecture. Estimated completion date January 2009.
 
The objective is to produce a normative update to the current CCOW specification that will describe the use of SAML within the CCOW architecture. Estimated completion date January 2009.
  
Motion: Rob moved that we approve the project proposal, CDS seconded the motion.
+
Motion: Rob moved that we approve the project proposal, CDS seconded the motion.  
 +
A friendly motion to define the term SAML was accepted.
 
<p><b>Vote - For – 7, Against – 0, Abstaining – 0 Motion Passed</b></p>
 
<p><b>Vote - For – 7, Against – 0, Abstaining – 0 Motion Passed</b></p>
  

Latest revision as of 21:09, 5 February 2008

SSD Steering Group

Minutes of Feb 04, 2008

NameOrganizationE-MailTC
John RitterIntel Corporation, Digital Health Groupjohn.ritter@intel.comEHR
R. Matthew SailorsThe Methodist Hospitalmsailors@tmhs.orgCDS, Arden
Seppala, GreggVAGregg.Seppala@va.govPA
Susan LeppingSiemens Medical Solutions Health Servicessusan.lepping@siemens.comFM
Patrick LoydGordon Point Informatics Ltd patrick.loyd@gpinformatics.com OO
Robert SeligerSentillion, Inc.robs@sentillion.com CCOW
David StaggsU.S. Department of Veterans Affairsdavid.staggs@va.govCCOW
Liora AlschulerAlschuler Assocliora@alschulerassociates.com SD
Calvin BeebeMayo Cliniccbeebe@mayo.eduSD

Agenda                                 Item Description

    Item 1: CCOW SAML Project Scope Statement
    Item 2: QRDA Project Scope Statement
    Item 3: P-to-P PHR Data Transfer Project Scope
    Item 4: Continua Project Scope Statement
    Item 5: EHR VR Profile Scope Statement
    Item 6: Quorum Rules

Project proposal was presented for the SAML support

Overview: The scope of the project is composed of the two tasks listed below. • To provide Context Participants a way to obtain SAML assertions about the user in context. • Establishing the user into context using a SAML assertion.

The objective is to produce a normative update to the current CCOW specification that will describe the use of SAML within the CCOW architecture. Estimated completion date January 2009.

Motion: Rob moved that we approve the project proposal, CDS seconded the motion. A friendly motion to define the term SAML was accepted.

Vote - For – 7, Against – 0, Abstaining – 0 Motion Passed

QRDA - Quality Reporting Document Architecture

Overview: The QRDA implementation guide will be based upon CDA and support the sharing of quality measure definitions between EHR systems. The group will be working in coordination with the Peds Data Standards SIG.


Motion: Liora moved that we approve the project proposal, SD seconded the motion.

Vote - For – 6, Against – 0, Abstaining – 0 Motion Passed


Plan-to-Plan Personal Health Record (PHR) Data Transfer Project

Overview: The goal of the Plan-to-Plan Personal Health Record (PHR) Data Transfer Project is to create an HL7 implementation guide that will provide for PHR portability between Health Plans. The project is limited in scope to the payor stakeholder community in the U.S. Realm. However it could be expanded or adapted to include other PHR stakeholders, data transfer beyond the PHR, and the international

Many of the AHIC plan members want to be able to share and maintain the information. CDA Implementation Guide and allow data to move between policy coverage.

Discussion: After some discussion, it was requested that some clarifications be provided on how the CDA document would be used in conjunction with the X12 standard. Additionly, the group requested clarification on the relationship this would have with the PHR functional model.

Action:

The project plan will be revised by SDTC and resubmitted the to the SSD - SD.  

Continua Implementation Guide for Personal Healthcare Monitoring Reports

Overview: With cooperation from Continua Health Alliance member companies and Electronic Medical Records software vendors, this project will develop an implementation guide constraining CDA Release 2. The implementation guide will specify CDA based representation of data/information (mostly containing analysed and raw information of data generated by personal healthcare monitoring devices such as glucometers, BP cuffs, thermometers, weight scales). The guide will be used by personal health management organizations (such as disease management organizations) to transfer remotely monitored patient data to electronic health records.

Motion: Liora approve to adopt the project scope statement, second: EHR.

Made by: Ritter, Second: Susan

Vote - For – 6, Against – 0, Abstaining – 0 Motion Passed

Electronic Health Record System Vital Records Functional Profile Project

Overview: The goal of the Electronic Health Record System Vital Records (VR) Functional Profile Project is to create an HL7 EHR-S Functional Profile that will facilitate leveraging electronic health record (EHR) systems to capture vital records (Birth and Death –related) data at the point of contact or point of care. The VR profile must articulate the functional requirements needed to support messaging among providers, states, local registrars and Federal agencies. The project will initially be U.S. Realm based; however it may be expanded to include international affiliates.

Motion: John approve to adopt the project scope statement, second by SD.

Made by: Ritter, Second: Susan

Vote - For – 6, Against – 0, Abstaining – 0 Motion Passed


Quorum

The group discussed our rules for quorum, action was tabled until the next working group meeting.