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

Difference between revisions of "20160217 arb minutes"

From HL7Wiki
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 24: Line 24:
 
#Other business and planning
 
#Other business and planning
 
##Next steps for FHIR to RIM RDF
 
##Next steps for FHIR to RIM RDF
−
##Work with Project services on sunset/withdrawal
+
##REDUX of "where does the product documentation go" [http://tscwiki.hl7.org/wiki/index.php?title=2016-02-15_TSC_Call_Agenda Redo document location]
−
###(From TSC minutes:
+
##[http://gforge.hl7.org/gf/project/arbgeneral/tracker/?action=TrackerItemEdit&tracker_item_id=9585 Work with Project services on sunset/withdrawal ]
−
Lynn here to discuss the sunsetting process for standards, particularly CCOW. 5 year period has expired with ANSI. Request has been to republish without ANSI accreditation. Lynn is against that option; republishing without ANSI stamp has multiple issues. If it's being used, it should be reaffirmed. Pat does not disagree. Tony states that INM had a negative comment on the reaffirmation based on the fact that the standard is not being worked on and it's not best practice anymore in the industry. That's the reason they didn't want to go forward with an ANSI reaffirmation. INM submitted a request for withdrawal and they wanted to know if we could retain it on the site as some people still use it. Ken: We asked ARB and Project Services to draft up a process for sunset to include this issue. We don't want a third option to posting standards; it's either an ANSI standard or it's not. But what does it look like to retire a standard? That is the question we're addressing. Paul states that CCOW may no longer be the best practice but if it is the practice in use then it needs to be supported. Ken: So we may want to continue to allow access to sunsetted standards but we won't be doing anything to maintain them. Pat: the other part is that Paul thinks it should be maintained as an active standard if people are using it, even if there's not a new version. Wayne: we shouldn't give the impression that we're actively supporting it. Ken: resubmitting it for ANSI certification doesn't seem to make sense, and maintaining it on our website just says it's available for use. Jean: By withdrawing it, it doesn't appear in our normative package - they can go back to previous normative editions to get it. Lynn will join the group to work on the document.
 
−
##Define location for HL7 documentation
 
 
#Adjournment
 
#Adjournment
  
Line 116: Line 114:
  
 
==Minutes==
 
==Minutes==
−
 
+
  DRAFT
−
 
+
# Grahame's understanding:
−
 
+
*  Liaise with all parts of the FHIR community (including committees, HL7 management, stakeholders, members) to ensure continued development of FHIR product and community
 +
*  Work with existing management and governance structures to build FHIR product and community
 +
*  Work with TSC to formalize the role and develop a job description
 +
*  Run the FHIR balloting and publishing process, and ensure business continuity around these arrangements (including documenting FHIR processes and procedures)
 +
**
 +
**Andy S: "Run the publishing process"  Director should oversee the publishing process.  Most product directors would NOT
 +
**Brian: Participate in the
 +
**Andy s: Input into, requirements for, publishing is an HQ process.
 +
**Lorraine: Traditionally separate preparation from publication.
 +
**Brian: Historically: Reassessed and adjusted.  FMG? Should be HQ, Grahame was showing Lynn how to run the build scripts.  Transfer is in progress.  Finding right language.
 +
*  Work with HL7 and the FHIR community to create the FHIR Foundation (http://fhir.org)
 +
*  Produce a monthly report documenting FHIR Product Director activities, issues and concerns
 +
#How is the Product director related to
 +
##SGB
 +
##Management Groups
 +
##Andy B: Market engagement?  Aligning with market segment, and relationship to key uses in the market.  Strategy and timelines, where is it heading, and why.
 +
##Lorraine: Align with HL7 strategy.  Management group aligns with timelines.
 +
##Andy B: Management group manages the conduct, product director provides leadership manages Direction and market engagement.
 +
##Zoran: Technology, or overall.
 +
##Andy B: Product, more than technology.  Features, Marketing, futures, relationship of product to the market.
 +
##Lorraine: Scope: Relationship of product director and the domain content groups
 +
##Andy B: Correct statement:  Is it applicable to all director roles, or specifics.
 +
##Lorraine: SGB is responsible for consistency across, director would make sure products meet the market needs, facilitate the management role. 
 +
##Paul: Evangelist rather than a gatekeeper.
 +
##Austin: Important in a democratic organization like HL7.
 +
##Andy B: Should imply a formal role - evangelist does not have that connotation.
 +
##Lorraine: Formal role: Promoter , but don't have the authority to force work, or halt work.
 +
##Dale: Points are how PD is related to SGB and management groups.  Comment that director manages the product more than the technology.
 +
##Andy B: Inclusive of both.
 +
##Dale: Should PD step back from technology?
 +
##Lorraine:  PD is a hat.  When you switch roles, you switch hats.
 +
##Zoran: PD product strategy.  What do we mean by technology in the role of the product director?
 +
##Lorraine: Relationship with other pieces.  We need to get Grahame's view.  Turn these notes into a document.  Who will finish the task? SGB or ARB.
 +
##Paul: SGB and PLA with ARB welcome to join in.
 +
##Lorraine: ARB provides how PD fits into the BAM.  SGB and PLA will make it fit in.
 +
##Austin: Joint discussion with Grahame - his viewpoint.  Convene here, or under SGB.  Being practical, ARB should host.
 +
# DOcument location:
 +
##NCPDP agreement allows the processes of the organization running the project to take place.
 +
##Iron out exception language.
 
[[Category:2015 Arb Minutes]]
 
[[Category:2015 Arb Minutes]]
 
[[Category:2016 Arb Minutes]]
 
[[Category:2016 Arb Minutes]]

Latest revision as of 21:01, 17 February 2016

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 and Minutes
  4. Methodology (60 minutes)
    1. What is the role of a product director.
  5. Other business and planning
    1. Next steps for FHIR to RIM RDF
    2. REDUX of "where does the product documentation go" Redo document location
    3. Work with Project services on sunset/withdrawal
  6. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20160217
Time: 5:00pm U.S. Eastern
Facilitator Julian, Tony/Constable, Lorraine Note taker(s) Julian, Tony//Constable, Lorraine
Attendee Name Affiliation
. Bond,Andy NEHTA
. Constable, Lorraine Constable Consulting Inc.
. Dagnall, Bo HP Enterprise Services
. Hufnagel, Steve ?????
. Hyland, Mario AEGIS
. Julian, Tony Mayo Clinic
. Knapp, Paul Pknapp Consulting
. Loyd, Patrick ICode Solutions
. Lynch, Cecil Accenture
. Milosevic, Zoran Deontik Pty Ltd
. Quinn, John Health Level Seven, Inc.
. Stechishin,Andy CANA Software and Service Ltd.
. Guests
. Mead, Charlie Vidal Group, Paris,France
. McDaniel, Mary Kay Cognosante
.
. Legend
X Present
. Absent
R Regrets
Quorum Requirements (Co-chair + 3) Met: Yes

Minutes

 DRAFT
  1. Grahame's understanding:
  • Liaise with all parts of the FHIR community (including committees, HL7 management, stakeholders, members) to ensure continued development of FHIR product and community
  • Work with existing management and governance structures to build FHIR product and community
  • Work with TSC to formalize the role and develop a job description
  • Run the FHIR balloting and publishing process, and ensure business continuity around these arrangements (including documenting FHIR processes and procedures)
    • Andy S: "Run the publishing process" Director should oversee the publishing process. Most product directors would NOT
    • Brian: Participate in the
    • Andy s: Input into, requirements for, publishing is an HQ process.
    • Lorraine: Traditionally separate preparation from publication.
    • Brian: Historically: Reassessed and adjusted. FMG? Should be HQ, Grahame was showing Lynn how to run the build scripts. Transfer is in progress. Finding right language.
  • Work with HL7 and the FHIR community to create the FHIR Foundation (http://fhir.org)
  • Produce a monthly report documenting FHIR Product Director activities, issues and concerns
  1. How is the Product director related to
    1. SGB
    2. Management Groups
    3. Andy B: Market engagement? Aligning with market segment, and relationship to key uses in the market. Strategy and timelines, where is it heading, and why.
    4. Lorraine: Align with HL7 strategy. Management group aligns with timelines.
    5. Andy B: Management group manages the conduct, product director provides leadership manages Direction and market engagement.
    6. Zoran: Technology, or overall.
    7. Andy B: Product, more than technology. Features, Marketing, futures, relationship of product to the market.
    8. Lorraine: Scope: Relationship of product director and the domain content groups
    9. Andy B: Correct statement: Is it applicable to all director roles, or specifics.
    10. Lorraine: SGB is responsible for consistency across, director would make sure products meet the market needs, facilitate the management role.
    11. Paul: Evangelist rather than a gatekeeper.
    12. Austin: Important in a democratic organization like HL7.
    13. Andy B: Should imply a formal role - evangelist does not have that connotation.
    14. Lorraine: Formal role: Promoter , but don't have the authority to force work, or halt work.
    15. Dale: Points are how PD is related to SGB and management groups. Comment that director manages the product more than the technology.
    16. Andy B: Inclusive of both.
    17. Dale: Should PD step back from technology?
    18. Lorraine: PD is a hat. When you switch roles, you switch hats.
    19. Zoran: PD product strategy. What do we mean by technology in the role of the product director?
    20. Lorraine: Relationship with other pieces. We need to get Grahame's view. Turn these notes into a document. Who will finish the task? SGB or ARB.
    21. Paul: SGB and PLA with ARB welcome to join in.
    22. Lorraine: ARB provides how PD fits into the BAM. SGB and PLA will make it fit in.
    23. Austin: Joint discussion with Grahame - his viewpoint. Convene here, or under SGB. Being practical, ARB should host.
  2. DOcument location:
    1. NCPDP agreement allows the processes of the organization running the project to take place.
    2. Iron out exception language.
Retrieved from "https://wiki.hl7.org/w/index.php?title=20160217_arb_minutes&oldid=115450"