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

Difference between revisions of "20121011 arb minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 22: Line 22:
 
#How to approach the SAIF Based FHIR IG?  
 
#How to approach the SAIF Based FHIR IG?  
 
#Product line references: (See [[20121004_arb_minutes | October 4 agenda]] for references.
 
#Product line references: (See [[20121004_arb_minutes | October 4 agenda]] for references.
## The SEI definition: A software product line (SPL) is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
+
** The SEI definition: A software product line (SPL) is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
## A standards product line is a set of specifications that share a common, managed set of capabilities satisfying the specified needs of a particular market segment and that are developed from a common set of core resources in a prescribed way.  
+
** A standards product line is a set of specifications that share a common, managed set of capabilities satisfying the specified needs of a particular market segment and that are developed from a common set of core resources in a prescribed way.  
## the above revised definition based on the SEI definition brings together the key design elements of common needs, common market segment, common base elements and common production methods.  HL7 will need to get a clear understanding of customer segmentation, probably based on objectives and technology stacks/skills in common before we can confirm product lines.  The capabilities could be enabled interoperability use cases driven from functional constraints.  The base elements and production methods relate to the methodologies and foundation elements, including original specification versions and their design principles.   
+
** the above revised definition based on the SEI definition brings together the key design elements of common needs, common market segment, common base elements and common production methods.  HL7 will need to get a clear understanding of customer segmentation, probably based on objectives and technology stacks/skills in common before we can confirm product lines.  The capabilities could be enabled interoperability use cases driven from functional constraints.  The base elements and production methods relate to the methodologies and foundation elements, including original specification versions and their design principles.   
 
#Adjournment
 
#Adjournment
  

Revision as of 18:23, 5 October 2012

ARB - Meeting (Date in Title)

logistics

Teleconferences are held on Tuesday at 4:00pm U.S. Eastern Schedules may be found at HL7.org Conference Call Center


Please join my meeting from your computer, tablet or smartphone.

  1. Join the meeting:
  2. If you cant use voip then capture the PIN from the screen for the above action, then
  • Weekly conference call.
  • For 24/7 customer service please call (844) 844-1322.

Agenda

  1. Call to order
  2. Roll Call
  3. Approval of Agenda
  4. Approval of Minutes
  5. Report from Architecture Project
  6. BAM
  7. Glossary and OWL representation
  8. Intersection of CIC and ArB definition of DAM
  9. How to approach the SAIF Based FHIR IG?
  10. Product line references: (See October 4 agenda for references.
    • The SEI definition: A software product line (SPL) is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
    • A standards product line is a set of specifications that share a common, managed set of capabilities satisfying the specified needs of a particular market segment and that are developed from a common set of core resources in a prescribed way.
    • the above revised definition based on the SEI definition brings together the key design elements of common needs, common market segment, common base elements and common production methods. HL7 will need to get a clear understanding of customer segmentation, probably based on objectives and technology stacks/skills in common before we can confirm product lines. The capabilities could be enabled interoperability use cases driven from functional constraints. The base elements and production methods relate to the methodologies and foundation elements, including original specification versions and their design principles.
  1. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 2012MMDD
Time: 4:00pm U.S. Eastern
Facilitator Charlie Mead/ Parker, Ron Note taker(s) Julian, Tony/????
Attendee Name Affiliation
. Bond,Andy NEHTA
. Constable, Lorraine Constable Consulting Inc.
. Curry, Jane Health Information Strategies
. Dagnall, Bo HP Enterprise Services
. Grieve, Grahame Health Intersections Pty Ltd
. Hufnagel, Steve U.S. Department of Defense, Military Health System
. Julian, Tony Mayo Clinic
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
. Mead, Charlie National Cancer Institute
. Milosevic, Zoran NEHTA
. Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
. Guests
.
. Legend
X Present
. Absent
R Regrets
Quorum Requirements Met: Yes

Minutes