20120115 arb WGM SanAntonio minutes

DRAFT

ArB Minutes

Detailed Agenda

Click here for meeting-at-a-glance

1. Sunday Q1
   1. Call to order
   2. Agenda and Minute approval
   3. Saif Canonical Ballot Reconcillation
      1. 19 comments
      2. 2 persuasive with mod
      3. 1 Persuasive
      4. 1 Considered- No action required
      5. 14 not related - an incorrect spreadsheet was uploaded by an affirmative balloter.
   4. Membership changes
   5. Glossary
   6. Next Steps
   7. Revisit Role
   8. Architecture Project
      1. FIM co-sponsorship
   9. OO project and Implications
      1. SOA representation
      2. Message representation
2. Sunday Q2
   1. Call to order
   2. Substantivity:
      1. This comes up because there is no substantive(ity) definition for non-wire format documents
      2. A substantive change is one that changes the semantics of a given specification, i.e. representational changes should <<not>> be considered substantive in the context of the source specification itself <<unless>> such representational changes could substantively change down-stream derivative products of the specification, including either/both derivative semantics and/or derivative serializations or other wire-format-sensitive constructs.
3. Sunday Q3
   1. Call to order
   2. V3 Substantive changes
   3. TBD
4. Tuesday Q4
   1. Call to order
   2. TBD
5. Wednesday Q1
   1. - Joint with SOA at SOA
6. Thursday Q3
   1. Call to order
   2. TBD
7. Thursday Q4
   1. Call to order
   2. Wrap up
   3. Agenda for future Telcons, etc.

Meeting Information

HL7 ArB Work Group Meeting Minutes Location: San Antonio, Texas, USA		Date: 20120115 Time: 9:00Am U.S. Eastern
Facilitator	Ron Parker	Note taker(s)	Julian, Tony
Attendee	Name	Affiliation
X	Bond,Andy	NEHTA
X	Curry, Jane	Health Information Strategies
X	Constable, Lorraine	Constable Consulting Inc.
X	Hufnagel, Steve	U.S. Department of Defense, Military Health System
X	Julian, Tony	Mayo Clinic
X	Dagnall, Bo	HP
X	Loyd, Patrick	ICode Solutions
X	Lynch, Cecil	Accenture
.	Mead, Charlie	National Cancer Institute
X	Milosevic, Zoran	NEHTA
.	Ocasio, Wendell	Agilex Technologies
X	Parker, Ron	CA Infoway
.	Quinn, John	Health Level Seven, Inc.
.	Guests
.	Laskso, Lynn	HL7 Staff
.	Legend
X	Present
.	Absent
Quorum Requirements Met: Yes

Minutes

1. Sunday Q1
   1. Call to order
   2. Agenda approval
      1. Motion Approve the agenda(Patrick/Jane)
      2. Vote (7-0-0)
   3. Saif Canonical Ballot Reconcillation
      1. 19 comments
      2. 2 persuasive with mod
      3. 1 Persuasive
      4. 1 Considered- No action required
      5. 14 not related - an incorrect spreadsheet was uploaded by an affirmative balloter.
      6. Motion to accept (Patrick/Jane)
      7. Vote 7-0-0
   4. Membership changes
      1. Patrick: Suggest addition of Lorraine Constable as she is involved in the OO project.
      2. Motion To add Lorraine (Patrick/Jane) (subject to approval by TSC).
      3. Vote (7-0-0)(Lorraine is not yet member)
      4. Patrick: Wish to remain on the ArB. Participation has been better.
      5. Grahame and John are not participating, and will step down.
      6. Current Membership: Patrick, Tony , Ron, Charlie, Andy, Zoran, Cecil, Jane, Steve, Lorraine, Bo Dagnal, Wendell
      7. Wiki profile page updates
         1. Logon to wiki
         2. Go to Special:ActiveUsers
         3. Find your name, and edit your user page
         4. Save!
   5. OO project and Implications
      1. SOA representation
      2. Message representation
      3. Add SAIF-AP update to weekly agenda.
   6. Glossary
      1. Glossary is incomplete.
      2. Cecil: Owl would provide representation for terminologies and glossaries.
      3. Tony: Definitions should be co-ordinated between WG's.
      4. Ron: ISO terms are well defined. HL7 needs tooling to provide a way to manage this. To architect a solution, all ballot content would spit out a list that would map against a glossary - managed in a semantic, such as OWL.
      5. Jane: Sounds like harmonization stuff, which has gone from Vocab to Rim to Patterns.
      6. Ron: Not on the publishing facilitators. TSC has reported that virtual harmonization has not worked well. This is an item for dedicated tooling.
      7. Patrick: The organization has not made the value proposition for virtual harmonization.
      8. Ron: Propose that we build a PSS around creating an HL7 Glossary.
      9. Motion To create a PSS for establishment of business and technical architecture to support active Glossary management. (Patrick/Jane)
      10. Volunteers - Ron, Jane, Cecil will take first class.
      11. Use SAIF to frame it -
          1. Business architecture
          2. Use Cases
          3. Processes affected
          4. Tooling required and intersection with current tooling
          5. Inputs
             1. Ballots
             2. Implementation Guides
             3. GOM
          6. Governance Implications
          7. Timeliness
      12. Vote(9-0-0)(Lorraine & Bo are now members)

Tony - Update the page to include Lorraine and Bo

1. Sunday Q2
   1. Call to order
   2. Architecture Project
      1. FIM co-sponsorship
      2. Steve Hufnafel: EHR workgroup has been working on EHR-S FM since 2006. The Project scope statement is for release 2.1 to add core information models for each of the system functions. It is straight-forward to build Information Model.
         1. Make EHR-S FM easier to user for analysts and engineers
         2. Verify and validate EHR-S FM Release 2.0
      3. Motion To approve ArB as co-sponsor as the PSS.(Steve/Patrick)
         1. ARB role - to review and clarify definitional items
         2. Help with alignment and mapping
         3. Test and potentially edit SAIF-CD
         4. Make Recommendations to TSC where conflict arises between content and other work groups.
      4. Vote (9-0-0)
2. Sunday Q3
   1. Call to order
   2. Substantivity:
      1. This comes up because there is no substantive(ity) definition for non-wire format documents
      2. 'A substantive change is one that changes the semantics of a given specification, i.e. representational changes should <<not>> be considered substantive in the context of the source specification itself <<unless>> such representational changes could substantively change down-stream derivative products of the specification, including either/both derivative semantics and/or derivative serializations or other wire-format-sensitive constructs.'
   3. Next Steps
   4. Revisit Role

1. 1. V3 Substantive changes
   2. TBD
2. Tuesday Q4
   1. Call to order
   2. TBD
3. Wednesday Q1
   1. Joint with SOA at SOA
4. Thursday Q3
   1. Call to order
   2. TBD
5. Thursday Q4
   1. Call to order
   2. Wrap up
   3. Agenda for future Telcons, etc.

Tony Julian 18:05, 15 January 2012 (UTC)