2014-09-08 TSC Call Agenda

From HL7 TSC
Revision as of 16:12, 8 September 2014 by Llaakso (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

TSC Agenda/Minutes

Meeting Info/Attendees

HL7 TSC Meeting Minutes

Location: call 770-657-9270 using code 985371#
NEW GoToMeeting ID: 426-505-829

Date: 2014-09-08
Time: 11:00 AM U.S. Eastern
Facilitator: Ken McCaslin Note taker(s): Lynn Laakso
Quorum = chair + 5 including 2 SD represented yes/no
Chair/CTO ArB International Affiliate Rep Ad-Hoc
x Ken McCaslin x Tony Julian . Jean Duteau x Austin Kreisler
x John Quinn x Lorraine Constable . Giorgio Cangioli .
Domain Experts Foundation and Technology Structure and Semantic Design Technical and Support Services
regrets Melva Peters x Woody Beeler x Calvin Beebe x Freida Hall
x John Roberts x Paul Knapp . Pat van Dyke x Andy Stechishin
ex officio Invited Guests Observers HL7 Staff
. Stan Huff (HL7 Chair) w/vote . x John Feikema x Lynn Laakso
. Don Mon (Vice Chair) vote . . . obs2 x Dave Hamill
. Chuck Jaffe (CEO) vote . . . .



  1. Introduction of visitors (including declaration of interests)
  2. Agenda review and approval -
  3. Approve Minutes of 2014-08-25 TSC Call Agenda


  1. Review action items
  2. Approval request for discussion:
  3. Approval items from e-vote: voting 6/0/0 with 2 Affiliate, ARB, DESD, SSD SD, T3SD
  4. For e-vote:
  5. Discussion topics:
  6. Reports: (attach written reports below from Steering Divisions et al.)
  7. Open Issues List


Minutes/Conclusions Reached:

  1. Introduction of visitors (including declaration of interests) Feik is observing in the event there are questions on FHIR and DAF
  2. Agenda review and approval - Lynn offers a publication request for CTS2
  3. Approve Minutes of 2014-08-25 TSC Call Agenda - approved by general consent


  1. Discussion topics:
    • Slot in a discussion time to review US Realm SI HL7 presentation - seeking 40 minutes. Minimum 20 minutes; Feik cannot attend Saturday but arrives midday Monday and will be available through lunch on Thursday. Paul can speak to this on Saturday and this has been assigned as homework.
  2. Approval request for discussion:
    • Project scope statement TEMPLATE for 2015 from Project Services of T3SD at TSC Tracker 3502, with list of changes
      • Dave Hamill reviews the document and notes that the bare template without instructions still needs to be developed.
      • Paul asks about the data types backwards compatibility section in 3.l. The intent was learning whether V3 projects are using Datatypes R2B. Discussion ensued. Decided to take out "including data types" and note "for V3 specifications, are you using the current data types" (yes/no with explanation). ACTION ITEM: Woody would provide a URL to current data type version for V3 and Dave will include the link in the instructions to verify use of the DT R2.
      • Ken would also like to remove "don't know". Austin disagrees that the project team may not have made the decision when the project is initiated. For V3 datatypes you might only want yes/no. For DSTU it is not even a requirement, notes Austin. Ken suggests "unknown" instead. This is met with agreement.
      • Austin suggests different phrasing such as implementable/processable e.g. stylesheets, schemas, etc. Group suggests "including schemas, transforms, stylesheets, executable programs, etc." Austin further suggests grouping it with the project risks above. Austin also suggests that Dave make it clear that the risk section repeats so they don't jam them all in one box. Ken suggests you add "if yes, are you preparing a security risk analysis"; Freida responds that it is in the FAQ. Austin notes that they may not know what they are producing yet so yes/no may not be sufficient e.g. unknown and N/A.
      • External vocabulary should be "include/reference" and make it y/n/unk/na
      • section 4 product added specifically for FHIR Implementation Guide but IG is specified in section 5 project intent and will we add IGs for other product families. Remove FHIR Implementation Guide.
      • What about the Logical Model as a product? Add that in. DIM is a V3 construct that could be labeled as such. For a new product family/definition please describe:
      • Project Approval Dates - add Affiliate to US Realm TF approval date.
      • Being over time, discussion concluded to be resumed on Saturday,
  3. Lynn reports some issues with normative ballots: current ballot levels not meeting quorum, CTS2 publication not ready, aECG reaffirmation. Paul notes we may want to remind cochairs on the Monday night of the 5 year issues and Steering Divisions can reinforce to WGs about the realm-specific projects go to task force first.

adjourned 12:11 PM

  1. Approval items from e-vote: voting 6/0/0 with 2 Affiliate, ARB, DESD, SSD SD, T3SD
  2. For e-vote:

Next Steps

Actions (Include Owner, Action Item, and due date)
  • .
Next Meeting/Preliminary Agenda Items

© 2014 Health Level Seven® International. All rights reserved.