2010-03-29 TSC Call Minutes

TSC Minutes 2010-03-29

HL7 TSC Meeting Minutes Location: call 770-657-9270 using code 124466# GoToMeeting ID: 165-215-206		Date: 2010-03-29 Time: 11:00 am - 12:00 pm EDT)
Facilitator	Charlie McCay	Note taker(s)	Lynn Laakso
Attendee	Name	Affiliation	Email Address
regrets	Calvin Beebe	HL7 SSD SD	cbeebe@mayo.edu
x	Woody Beeler	HL7 FTSD	woody@beelers.com
x	Bob Dolin	HL7 Board Chair	BobDolin@gmail.com
x	Austin Kreisler	HL7 DESD	austin.j.kreisler@saic.com
x	Lynn Laakso (scribe, non-voting)	HL7 HQ	lynn@hl7.org
x	Ken McCaslin	HL7 TSS SD	Kenneth.H.McCaslin@QuestDiagnostics.com
x	Charlie McCay (chair)	HL7 TSC Chair	charlie@ramseysystems.co.uk
regrets	Charlie Mead	HL7 ArB Chair	meadch@mail.nih.gov
regrets	Ravi Natarajan	HL7 Affiliate	Ravi.Natarajan@nhs.net
x	Ron Parker	HL7 ArB Alternate	rparker@infoway-inforoute.ca
x	John Quinn	HL7 CTO	jquinn@hl7.org
x	Gregg Seppala	HL7 SSD SD Alternate	gregg.seppala@va.gov
x	Helen Stevens	HL7 TSS SD Alternate	helen.stevens@shaw.ca
x	Ed Tripp	HL7 DESD Alternate	Edward.tripp@estripp.com
x	D. Mead Walker	HL7 FTSD Alternate	dmead@comcast.net
			.
Quorum Requirements (Co-chair +5 with 2 SD Reps) Met: (yes/No)

Agenda Topics

1. Introduction of visitors (including declaration of interests)
2. Accept Agenda –
3. Approve Minutes from 2010-03-22_TSC_Call_Minutes
4. Review action items –
5. CEO Report –
6. CTO Report - and Fridsma's Presentation
7. ArB Report – worked on schedule for Rio; no further report.
8. Affiliates Report –
9. Domain Experts –
10. Foundation & Technology –
    • Motion: to approve scope statement for Security WG's Security and Privacy Ontology Project at TSC Tracker # 1478
11. Structure & Semantic Design –
12. Technical & Support Services -
13. WGM Planning
14. Organizational Relations Committee update (semiweekly)
15. Discussion Topics:

    Next week's call cancelled? Two projects outstanding - postpone to 4/12 or e-vote?

    • Open Issues List
    • Ballot title change request, CDS would like to change the title as it might better match the ballot contents if the name had "UML Model" removed). This is because the implementation guide contains more than just the UML model. In fact, for this cycle, the main content is content other than the UML model, which we expect will be included in the next ballot cycle.
      • Request to change

        HL7 Version 3 Implementation Guide: Virtual Medical Record for Clinical Decision Support; (vMR-CDS) UML Model for GELLO, Release 1 (1st Informative Ballot),

      • to

        HL7 Version 3 Implementation Guide: Virtual Medical Record for Clinical Decision Support; (vMR-CDS) for GELLO, Release 1 (1st Informative Ballot); logged at TSC Tracker # 1479

    • V2.6 and 2.7 errata for TSC discussion TSC tracker #1523 - There are two options for moving the V2.7 ballot forward:
      1. Publish the flawed document with an errata
         • Publish the flawed document accompanied by an errata that explains the problematic fields, how to use them correctly to maintain backwards compatibility, and noting that they will be corrected in V2.8 (and publish errata for 2.6). If Frank is agreeable to this approach and will withdraw his negative, we can publish V2.7
           • All of the voters in the consensus pool should be advised of the issue. We might want to conduct a re-circulation ballot as a means of advising the ballot pool of the errata solution and letting them vote on whether that is an acceptable resolution.
         • If Frank is not agreeable to this approach and won’t withdraw his negative, we will conduct a re-circulation ballot that acknowledges the problem described by the outstanding negative but offers up the errata as the solution. If this ballot passes, we can publish V2.7. If this ballot does not pass, we will have to correct the flaws and conduct another normative ballot.
      2. Correct the flaws now and conduct another normative ballot on 2.7 and publish errata for 2.6.
    • HL7 Security Considerations - Cookbook, at TSC Tracker # 1513
      • Link to wiki site http://wiki.hl7.org/index.php?title=Cookbook_for_Security_Considerations

Supporting Documents

1. Fridsma's Presentation - http://gforge.hl7.org/gf/download/docmanfileversion/5543/7074/Fridsma_IS_framework_for_HITSC.ppt, or http://mycourses.med.harvard.edu/ec_res/nt/75489D65-B131-4010-B11B-68D4198E8C2A/Fridsma_IS_framework_for_HITSC.ppt

Minutes/Conclusions Reached:

1. Visitors:none
2. Agenda: add planning call for next week. Something from Publishing, revisit discussion from changing DSTU to Informative. Left it to the Work Group's initiative to bring it to TSC if they wish to appeal. Brought it to Steering Division. Will report during FTSD. Agenda accepted.
3. Minutes approved by general consent
4. CEO - no report
5. CTO Report - and Fridsma's Presentation
   • HITSP sent out email on stuff from Halamka, with link to Fridsma's presentation, two separate meetings in D.C. at which it was presented. It talks about an Interoperability Framework for the U.S., describes state and regional HIEs, and a new NHIN Direct. Looking for clarification document to come out of ONC. Formally going with contractors to define use cases, then to one or more SDOs to build specifications. This lists the SAIF as their Interoperability Framework, which he feels is based on efforts of NCI. Ron joins the call. He feels we need info on the SAIF on the web page right away as people will be looking for it. Austin notes in looking a NIEM and sees it as a content standard for XML - asks if we are looking at converting all existing standards into XML? John thinks if we have a common reference information model it's possible. X12 probably cannot make the transition easily. Are we talking about a different wire representation. OMB supports the NIEM methodology. Will be something between RESTful and what we have now. Probably need common wrappers for V2. NIEM is also recognized unsupportive of terminology.
6. ArB - per CMead, worked on schedule for Rio; no further report.
7. Affiliates:
8. DESD
9. FTSD
   • Motion: to approve scope statement for Security WG's Security and Privacy Ontology Project at TSC Tracker # 1478
10. SSD SD
11. T3SD
12. WGM Planning
13. Organizational Relations Committee update (semiweekly)
14. Discussion

• Ballot title change request, CDS would like to change the title as it might better match the ballot contents if the name had "UML Model" removed). This is because the implementation guide contains more than just the UML model. In fact, for this cycle, the main content is content other than the UML model, which we expect will be included in the next ballot cycle.
  • Request to change

    HL7 Version 3 Implementation Guide: Virtual Medical Record for Clinical Decision Support; (vMR-CDS) UML Model for GELLO, Release 1 (1st Informative Ballot),

  • to

    HL7 Version 3 Implementation Guide: Virtual Medical Record for Clinical Decision Support; (vMR-CDS) for GELLO, Release 1 (1st Informative Ballot); logged at TSC Tracker # 1479

• V2.6 and 2.7 errata for TSC discussion TSC tracker #1523 - There are two options for moving the V2.7 ballot forward:
  1. Publish the flawed document with an errata
     • Publish the flawed document accompanied by an errata that explains the problematic fields, how to use them correctly to maintain backwards compatibility, and noting that they will be corrected in V2.8 (and publish errata for 2.6). If Frank is agreeable to this approach and will withdraw his negative, we can publish V2.7
       • All of the voters in the consensus pool should be advised of the issue. We might want to conduct a re-circulation ballot as a means of advising the ballot pool of the errata solution and letting them vote on whether that is an acceptable resolution.
     • If Frank is not agreeable to this approach and won’t withdraw his negative, we will conduct a re-circulation ballot that acknowledges the problem described by the outstanding negative but offers up the errata as the solution. If this ballot passes, we can publish V2.7. If this ballot does not pass, we will have to correct the flaws and conduct another normative ballot.
  2. Correct the flaws now and conduct another normative ballot on 2.7 and publish errata for 2.6.

• HL7 Security Considerations - Cookbook, at TSC Tracker # 1513
  • Link to wiki site http://wiki.hl7.org/index.php?title=Cookbook_for_Security_Considerations

1. Adjourned hh:mm am/pm (timezone).

Actions (Include Owner, Action Item, and due date) .

Next Meeting/Preliminary Agenda Items .