Difference between revisions of "20080618 arbJumpStartminutes"

From HL7Wiki
Jump to navigation Jump to search
(New page: ==Attendees== * Charlie Mead * Nancy Orvis * AbdulMalik Shakir * Tony Julian * Jane Curry * John Quinn * Scott Robertson * Galen Mulrooney * Rich Rogers ==Minutes== * Discussion of deliv...)
 
m
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Attendees==
+
{{Arb_Old_Minutes}}
* Charlie Mead
+
'''Architecture Board'''
* Nancy Orvis
 
* AbdulMalik Shakir
 
* Tony Julian
 
* Jane Curry
 
* John Quinn
 
  
* Scott Robertson
+
Minutes of the 20080618 June out-of-cycle Day 3
* Galen Mulrooney
+
 
* Rich Rogers
+
 
 +
==Attendance==
 +
<table border="1"><tr><td>Name</td><td>Role</td><td>Affiliation</td><td>email</td></tr>
 +
<tr><td>Charlie, Mead </td><td> ArB </td><td>Booz Allen Hamilton</td><td>charlie.mead@booz.com</td></tr>
 +
<tr><td>Curry, Jane </td><td> ArB  </td><td>Health Information Strategies</td><td>janecurry@healthinfostrategies.com</td></tr>
 +
<tr><td>Julian, Tony </td><td> ArB </td><td>Mayo Clinic</td><td>ajulian@mayo.edu</td></tr>
 +
<tr><td>Koisch, John  </td><td> ArB </td><td>Boz</td><td>koisch_john@bah.com</td></tr>
 +
<tr><td>Mulrooney, Galen </td><td> guest </td><td>VHA</td><td>galen.mulrooney@med.va.gov</td></tr>
 +
<tr><td>Orvis, Nancy </td><td> ArB</td><td>DOD</td><td>nancy.orvis@tma.osd.mil</td></tr>
 +
<tr><td>Quinn, John </td><td> ArB</td><td>Health Level Seven, Inc.</td><td>jquinn@HL7.org</td></tr>
 +
<tr><td>Rogers, Rich </td><td> guest </td><td>IBM</td><td>rrogers@us.ibm.com</td></tr>
 +
<tr><td>Robertson, Scott</td><td>guest</td><td>Kaiser Permanente</td><td>scott.robertson@kp.com</td></tr>
 +
<tr><td>Shakir, Abdul-Malik </td><td> ArB </td><td>Shakir Consulting</td><td>ShakirConsulting@cs.com</td></tr>
 +
</table>
 +
 
 +
==Agenda==
 +
* refine scope statement - more concrete
 +
** focused mon Services approach for HL7
 +
** Relate to Dynamic Model
 +
*** Dynamic Model is where HL7 is lacking
 +
*** HSSP creates / if focused on SFM a functional requirements document which, currently, gets thrown over the fence to OMG; have to get to implementable spec
  
 
==Minutes==
 
==Minutes==
* Discussion of deliverables for September.
+
* Discussion of topics for September. Needs to be aligned with the
 
** Dynamic Framework
 
** Dynamic Framework
 
** Service Taxonomy Ftramework
 
** Service Taxonomy Ftramework
 +
** Service Description / Contract / Metadata
 +
** Service Roadmap
 
** Service Specification Methodology (including artifacts)
 
** Service Specification Methodology (including artifacts)
** Use of Static Semantics (IM, Vocab)
+
** Use of Static Semantics (IM, Vocab, DT's)
 +
*** Take EHR FM as a starting point for semantics where appropriate
 
** Implementation Guides
 
** Implementation Guides
 
** Communication Plan
 
** Communication Plan
Line 23: Line 41:
 
** Next Steps
 
** Next Steps
 
** Governance
 
** Governance
 
+
* Current HSSP Practice
* Prioritized List
+
** RLUS
 +
** EIS
 +
** Decision Support
 +
** Clinical Research Filter Query
 +
** But no progress on the OMG side, Only functional spec, still need the implementable spec
 +
** John Q's request wants to have implementable spec coming out of HL7, at least a Platform Independent Specification
 +
* Charlie:  "Separate choreography from orchestration"
 +
** choreography = how things can interact
 +
** orchestration = proscriptive, must be done this way
 +
** BPL - orchestration tool, static structure for runtime, very defined, very specific
 +
** another analogy:
 +
*** orchestration = a string of beads
 +
*** choreography = the beads and rules on how they can be strung together
 +
* Prioritized List (and status, existing work threads)
 
** Governance
 
** Governance
 +
*** tbBAM, including the role of ArB (which is not specified today)
 +
*** Conformance Class Model
 
** Dynamic Framework
 
** Dynamic Framework
 +
*** Ongoing project with JK and GG
 
** Service Specification Methodology (including artifacts)
 
** Service Specification Methodology (including artifacts)
 +
*** Relevant work form Infoway, DoD, NCI
 
** Examples
 
** Examples
 +
 +
* AMS: we should approach other SDO's to discuss service specification and the intersection of MDA and services
 +
[[Category:Arb Old Minutes]]  [[User:ajulian|Tony Julian]]

Latest revision as of 21:37, 19 March 2010

Architecture Board

Minutes of the 20080618 June out-of-cycle Day 3


Attendance

NameRoleAffiliationemail
Charlie, Mead ArB Booz Allen Hamiltoncharlie.mead@booz.com
Curry, Jane ArB Health Information Strategiesjanecurry@healthinfostrategies.com
Julian, Tony ArB Mayo Clinicajulian@mayo.edu
Koisch, John ArB Bozkoisch_john@bah.com
Mulrooney, Galen guest VHAgalen.mulrooney@med.va.gov
Orvis, Nancy ArBDODnancy.orvis@tma.osd.mil
Quinn, John ArBHealth Level Seven, Inc.jquinn@HL7.org
Rogers, Rich guest IBMrrogers@us.ibm.com
Robertson, ScottguestKaiser Permanentescott.robertson@kp.com
Shakir, Abdul-Malik ArB Shakir ConsultingShakirConsulting@cs.com

Agenda

  • refine scope statement - more concrete
    • focused mon Services approach for HL7
    • Relate to Dynamic Model
      • Dynamic Model is where HL7 is lacking
      • HSSP creates / if focused on SFM a functional requirements document which, currently, gets thrown over the fence to OMG; have to get to implementable spec

Minutes

  • Discussion of topics for September. Needs to be aligned with the
    • Dynamic Framework
    • Service Taxonomy Ftramework
    • Service Description / Contract / Metadata
    • Service Roadmap
    • Service Specification Methodology (including artifacts)
    • Use of Static Semantics (IM, Vocab, DT's)
      • Take EHR FM as a starting point for semantics where appropriate
    • Implementation Guides
    • Communication Plan
    • Tooling Requirements
    • Examples
    • Next Steps
    • Governance
  • Current HSSP Practice
    • RLUS
    • EIS
    • Decision Support
    • Clinical Research Filter Query
    • But no progress on the OMG side, Only functional spec, still need the implementable spec
    • John Q's request wants to have implementable spec coming out of HL7, at least a Platform Independent Specification
  • Charlie: "Separate choreography from orchestration"
    • choreography = how things can interact
    • orchestration = proscriptive, must be done this way
    • BPL - orchestration tool, static structure for runtime, very defined, very specific
    • another analogy:
      • orchestration = a string of beads
      • choreography = the beads and rules on how they can be strung together
  • Prioritized List (and status, existing work threads)
    • Governance
      • tbBAM, including the role of ArB (which is not specified today)
      • Conformance Class Model
    • Dynamic Framework
      • Ongoing project with JK and GG
    • Service Specification Methodology (including artifacts)
      • Relevant work form Infoway, DoD, NCI
    • Examples
  • AMS: we should approach other SDO's to discuss service specification and the intersection of MDA and services Tony Julian