This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "20080814 arb minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 18: Line 18:
 
== Minutes ==
 
== Minutes ==
 
* Agenda  
 
* Agenda  
** tuesday 0815
+
** tuesday 0800 - 1130
 
+
***Artifacts for SOA
 
+
****How SOA artifacts are diffferent, how they map to the FW, how they map to the FW
 
+
****Traceability from Requirements to Design to Implementation (Traceability across artifacts)
 +
****HDF is not very affected by srvices per se, so need to show in S4 how unique SOA Artifacts support different aspects of the HDF
 +
*****Include COPPA Information Model work / Constraint Pattern from te NCI
 +
***tbBAM  - Structure of HL7 delivers support for customers to craft ISCS
 +
****Different groups need to expose XYZ artifacts to appropriately utilize/ support / give back to the HL7 Capability list ... it is a QA issue when standards are in process. It is not sufficient to simply rely on automated tooling (but we should def leveraged where we can). Capacity and Capability. We need to identify the "how to" as well as the phase transitions that are _easier_ and properly granulated. Empower the feedback loop from implementation back to specification development.
 +
** Wednesday 0800 - 1130
 
*** ISPS
 
*** ISPS
 
 
***Taxonomy of Services
 
***Taxonomy of Services
 
 
***OHT Modeling project for HL7 - Lessons Learned (Rogers)
 
***OHT Modeling project for HL7 - Lessons Learned (Rogers)
 
 
***Meta Model Review, UPMS Profile
 
***Meta Model Review, UPMS Profile
 
+
** Thursday 0800 - 1130
 +
***Relationships between HL7 and other Organizations that needs to be revisited or added
 
***Communication Plan
 
***Communication Plan
 
****What are we going to say and to whom?
 
****What are we going to say and to whom?
 
**** Develop 1-3 powerpoint presentations  
 
**** Develop 1-3 powerpoint presentations  
***Artifacts for SOA
+
*** Assignments, Ownerships
 +
*** Review Schedule
 +
**** September 11th is drop dead date for readiness for the meeting; final review
 +
 
 +
 
 +
 
  
****How SOA artifacts are diffferent, how they map to the FW, how they map to the FW
 
****Traceability from Requirements to Design to Implementation (Traceability across artifacts)
 
****HDF is not very affected by srvices per se, so need to show in S4 how unique SOA Artifacts support different aspects of the HDF
 
*****Include COPPA Information Model work / Constraint Pattern from te NCI
 
  
***Relationships between HL7 and other Organizations that needs to be revisited or added
 
*** Assignments, Ownerships
 
***Review Schedule
 
**** September 11th is drop dead date for readiness for the meeting; final review
 
  
  
  
 
== Action Items ==
 
== Action Items ==

Revision as of 20:03, 14 August 2008

Attendees

  • John Koisch
  • Rich Rogers
  • Tony Julian
  • Jane Curry
  • Dave Hammill
  • Steve Hufnagel
  • Ron Parker
  • Abdul Malik Shakir

Agenda

  • Finalize agenda for next week
  • Finalize roster for next week
  • Finalize homework for next week

Minutes

  • Agenda
    • tuesday 0800 - 1130
      • Artifacts for SOA
        • How SOA artifacts are diffferent, how they map to the FW, how they map to the FW
        • Traceability from Requirements to Design to Implementation (Traceability across artifacts)
        • HDF is not very affected by srvices per se, so need to show in S4 how unique SOA Artifacts support different aspects of the HDF
          • Include COPPA Information Model work / Constraint Pattern from te NCI
      • tbBAM - Structure of HL7 delivers support for customers to craft ISCS
        • Different groups need to expose XYZ artifacts to appropriately utilize/ support / give back to the HL7 Capability list ... it is a QA issue when standards are in process. It is not sufficient to simply rely on automated tooling (but we should def leveraged where we can). Capacity and Capability. We need to identify the "how to" as well as the phase transitions that are _easier_ and properly granulated. Empower the feedback loop from implementation back to specification development.
    • Wednesday 0800 - 1130
      • ISPS
      • Taxonomy of Services
      • OHT Modeling project for HL7 - Lessons Learned (Rogers)
      • Meta Model Review, UPMS Profile
    • Thursday 0800 - 1130
      • Relationships between HL7 and other Organizations that needs to be revisited or added
      • Communication Plan
        • What are we going to say and to whom?
        • Develop 1-3 powerpoint presentations
      • Assignments, Ownerships
      • Review Schedule
        • September 11th is drop dead date for readiness for the meeting; final review





Action Items