Difference between revisions of "20110810 SAIF AP ConCall"
(Created page with "=SAIF Architecture Program – 2011-08-10 Meeting= Return to SAIF Architecture Program Wiki Home Page<br\> Return to [http://wiki.hl7.org/index.php?...") |
|||
(19 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
*Dates: Weekly on Wednesdays | *Dates: Weekly on Wednesdays | ||
*Time: 10:00 - 11:00 Eastern | *Time: 10:00 - 11:00 Eastern | ||
− | *Phone Number: +1 ( | + | *Phone Number: +1 (706) 634-4215 NOTE: This call is using the pilot conference calling number!!! |
*Participant Passcode: 124466 | *Participant Passcode: 124466 | ||
*Web Coordinates: https://www2.gotomeeting.com/join/768017802 Meeting ID: 768-017-802 | *Web Coordinates: https://www2.gotomeeting.com/join/768017802 Meeting ID: 768-017-802 | ||
Line 14: | Line 14: | ||
#Role Call | #Role Call | ||
#Agenda Review | #Agenda Review | ||
− | # | + | #Adoption Process Document updates from Project Services '''(Haddorff)''' ( [http://gforge.hl7.org/gf/download/docmanfileversion/6389/8559/HL7AdoptionProcess_draftV10.doc HL7AdoptionProcess_draftV10.doc] ) |
+ | ##Peer Review comment spreadsheet form adapted from Ballot Comment spreadsheet( [http://gforge.hl7.org/gf/download/docmanfileversion/6374/8530/Reviewcomments_ArtifactName_draftV1.xls Review comments_ArtifactName_draft1.xls] ) | ||
+ | ###Developed by Project Services at suggestion of SAIF AP in conjunction with proposed adoption process | ||
+ | #Prepping for the Sept WGM Meeting | ||
+ | ##Present what needs to be done for a RASCI chart (which will be a Sept WGM agenda item) (Haddorff) | ||
+ | ##SD WG Tuesday Q3 session in San Diego (CDA R3 and SAIF) – invite SAIF AP people to attend that, if interested. | ||
# | # | ||
#Recurring Agenda Items | #Recurring Agenda Items | ||
− | ## | + | ## New Agenda items for San Diego Sept. WGM – Wednesday Q4: [[20110914_SAIF_AP_Meeting]] |
− | + | ###Add the following to the Agenda: SAIF and Sound White paper??? | |
##Pilot Coordination updates '''(Rick Haddorff)''' | ##Pilot Coordination updates '''(Rick Haddorff)''' | ||
###Any new Coordination items? '''(Team)''' | ###Any new Coordination items? '''(Team)''' | ||
Line 24: | Line 29: | ||
#Action item review (see below) | #Action item review (see below) | ||
#Next steps | #Next steps | ||
+ | #Please complete the conference calling pilot [http://www.surveymonkey.com/s/W8VLJ2H survey]. Next week starts the pilot of the new platform | ||
===Action Items to Review=== | ===Action Items to Review=== | ||
− | *''' | + | *'''None to review |
− | |||
− | |||
[http://gforge.hl7.org/gf/project/saif-arch-pgm/tracker/?action=&br_trackerssort_by=tracker.DESCRIPTION&br_trackerssort_order=asc Link to the Complete List of Action Items/Issues/Risks (GForge)] | [http://gforge.hl7.org/gf/project/saif-arch-pgm/tracker/?action=&br_trackerssort_by=tracker.DESCRIPTION&br_trackerssort_order=asc Link to the Complete List of Action Items/Issues/Risks (GForge)] | ||
+ | |||
+ | |||
+ | ===Meeting Attendees=== | ||
+ | X=Present on Call | ||
+ | {|- | ||
+ | {|border="1" cellpadding="2" cellspacing="0" | ||
+ | |- | ||
+ | | border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"| | ||
+ | |- | ||
+ | <!-- ******** CHANGE chair and scribe ON NEXT LINES *******************--> | ||
+ | | width="10%" colspan="1" align="right"|'''Facilitator''' | ||
+ | | width="35%" colspan="1" align="left"|Austin Kreisler | ||
+ | | width="25%" colspan="1" align="right"|'''Note taker(s)''' | ||
+ | | width="30%" colspan="1" align="left"|David Hamill | ||
+ | |- | ||
+ | | border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"| | ||
+ | |- | ||
+ | | border="1" cellpadding="2" colspan="1" align="left"|'''Attendee''' | ||
+ | | '''Name''' | ||
+ | |colspan="2"|'''Affiliation''' | ||
+ | |||
+ | <!---============================================================================== | ||
+ | | | | ||
+ | | AAAA TTTTTT TTTTTT EEEEEE NN NN DDDDD EEEEEE EEEEEE SSSSS | | ||
+ | | AA AA TT TT EE NNN NN DD DD EE EE SS | | ||
+ | | AAAAAA TT TT EEEE NN NN NN DD DD EEEE EEEE SSSS | | ||
+ | | AA AA TT TT EE NN NNN DD DD EE EE SS | | ||
+ | | AA AA TT TT EEEEEE NN NN DDDDD EEEEEE EEEEEE SSSSS | | ||
+ | | | | ||
+ | ===============================================================================---> | ||
+ | |- | ||
+ | <!-- ********add attendee information here *********--> | ||
+ | |X|| Austin Kreisler | ||
+ | |colspan="2"| TSC Chair | ||
+ | |- | ||
+ | | || Brian Pech | ||
+ | |colspan="2"| Interested Participant | ||
+ | |- | ||
+ | |X|| David Hamill | ||
+ | |colspan="2"| HL7 HQ / Program Manager | ||
+ | |- | ||
+ | ||| Ed Tripp | ||
+ | |colspan="2"| Domain Experts SD \ TSC | ||
+ | |- | ||
+ | | || Gregg Seppala | ||
+ | |colspan="2"| Product Quality Plan Project | ||
+ | |- | ||
+ | | || Jane Curry | ||
+ | |colspan="2"| Tooling | ||
+ | |- | ||
+ | | || Jim McClay | ||
+ | |colspan="2"| Emergency Care | ||
+ | |- | ||
+ | | || John Moehrke | ||
+ | |colspan="2"| Security Cookbook | ||
+ | |- | ||
+ | | || John Quinn | ||
+ | |colspan="2"| HL7 CTO | ||
+ | |- | ||
+ | | || Lloyd McKenzie | ||
+ | |colspan="2"| MnM Work Group / SAIF Implementation Guide Pjt | ||
+ | |- | ||
+ | | || Lorraine Constable | ||
+ | |colspan="2"| Composite Order Pjt \ OO Behavioral Framework Pjt | ||
+ | |- | ||
+ | | || Patrick Loyd | ||
+ | |colspan="2"| OO Work Group / Composite Order Pjt | ||
+ | |- | ||
+ | |X|| Rick Haddorff | ||
+ | |colspan="2"| Project Services WG / SAIF Pilot Coordination Pjt | ||
+ | |- | ||
+ | | || Robert Lario | ||
+ | |colspan="2"| Object Management | ||
+ | |- | ||
+ | |X|| Pat Van Dyke | ||
+ | |colspan="2"| EHR WG | ||
+ | |- | ||
+ | |X|| Steve Hufnagel | ||
+ | |colspan="2"| ArB / SAIF Book Project / SOA | ||
+ | |- | ||
+ | | || Wendy Huang | ||
+ | |colspan="2"| Implementation Conformance WG | ||
+ | |- | ||
+ | | || Gary Dickinson | ||
+ | |colspan="2"| EHR WG | ||
+ | |- | ||
+ | | || Freida Hall | ||
+ | |colspan="2"| Project Services WG | ||
+ | |- | ||
+ | |colspan="4" style="background:#f0f0f0;"| | ||
+ | |- | ||
+ | <!-- ***** Delete instructions and change quorum requirements ON NEXT LINE *****--> | ||
+ | |colspan="4" |'''Quorum Requirements Met: '''No | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | ===Minutes=== | ||
+ | <!---================================================================ | ||
+ | | | | ||
+ | | MM MM IIIIII NN NN UU UU TTTTTT EEEEEE SSSSS | | ||
+ | | MMM MMM II NNN NN UU UU TT EE SS | | ||
+ | | MM MMM MM II NN NN NN UU UU TT EEEE SSSS | | ||
+ | | MM M MM II NN NNN UU UU TT EE SS | | ||
+ | | MM MM IIIIII NN NN UUUU TT EEEEEE SSSSS | | ||
+ | | | | ||
+ | =================================================================---> | ||
+ | <!-- <br/> carriage break to copy ******--> | ||
+ | |||
+ | '''Minutes/Conclusions Reached:'''<br/> | ||
+ | |||
+ | |||
+ | '''Adoption Process Document updates'''<br/> | ||
+ | <br/> | ||
+ | Re: the following update in the document:<br/> | ||
+ | *Removing the requirement that a Project Scope Statement must be created. Additionally, a paragraph was included explaining instances where a PSS is not required along with Pros/Cons of creating a PSS. | ||
+ | *Austin: Add another line focusing on if another Work Group is adversely impacted by a WG’s internal process, they can petition the TSC and recommend that a Project Scope Statement be created since the proposed process is not internal just to the one WG. | ||
+ | <br/> | ||
+ | Re: Verbiage focusing on Comment Only is subject to ANSI balloting rules may be incorrect. Project Services will research. | ||
+ | *Austin added the following: | ||
+ | *Con for non-ballot approaches: Runs the risk of not getting people’s attention | ||
+ | *Pro for Comment Only Ballot: Get’s people’s attentions better | ||
+ | <br/> | ||
+ | *Austin: A lot of Mandated HL7 processes are not part of the WG Health Metrics. Hence, change this to ‘are candidates for WG Health Metrics’ instead of ‘will’ | ||
+ | *Regarding the Outstanding Issue indicating that a Work Group should create and maintain a Wiki Page for Informal Ballot Comments, the group agreed that this should be removed, and allow WG’s to decide how they want to do that. | ||
+ | |||
+ | |||
+ | |||
+ | '''Peer Review comment spreadsheet form adapted from Ballot Comment spreadsheet'''<br/> | ||
+ | *SAIF AP Team should review the document and provide feedback. | ||
+ | *The goal of the spreadsheet is to capture and reconcile comments submitted regarding the proposed process for adoption. | ||
+ | |||
+ | |||
+ | '''Prepping for the Sept 2011 WGM Meeting'''<br/> | ||
+ | *Rick reviewed the RASCI chart today. | ||
+ | *Once active, may want to do the RASCI chart retroactively | ||
+ | *Rick will work with CDA R3 as the pilot for the RASCI chart and hopefully will have it completed enough to present at the Sept 2011 WGM. | ||
+ | *SAIF and Sound Whitepaper update: It’s dependant on MnM completing work on the artifact definition. Hence there probably won’t be much to report on at the September 2011 WGM. | ||
+ | |||
+ | <br/>Gforge Accounts can be requested via: | ||
+ | http://gforge.hl7.org/gf/account/?action=UserAdd | ||
+ | |||
+ | ''Adjourned 10:55 AM Eastern Time | ||
+ | |||
+ | ===New Action Items === | ||
+ | <!-- <br/> carriage break to copy ******--> | ||
+ | Rick – Add a line based on Austin’s suggestion about if another Work Group is adversely impacted by a WG’s internal process, they can petition the TSC and recommend that a Project Scope Statement be created since the proposed process is not internal just to the one WG. | ||
+ | <br/> | ||
+ | Rick – Wordsmith Change to the Adoption Process document ‘defining a Project Scope Statement’ to ‘creating a Project Scope Statement’ | ||
+ | <br/> | ||
+ | Rick – Follow up regarding the Adoption Process verbiage focusing on “Comment Only is subject to ANSI balloting rules” as this may be incorrect. | ||
+ | <br/> | ||
+ | Rick – Add the Pros/Cons regarding getting people’s attention | ||
+ | <br/> | ||
+ | Rick – Re: Not all mandated HL7 processes are not part of the WG Health Metrics. Hence, change this to ‘are candidates for WG Health Metrics’ instead of ‘will’ | ||
+ | <br/> | ||
+ | Rick – Remove the Outstanding Issue indicating that a Work Group should create and maintain a Wiki Page for Informal Ballot Comments | ||
+ | <br/> | ||
+ | Austin/Rick – Have Rick attend a CDA R3 call to bring forward the RASCI work to that project. |
Latest revision as of 17:49, 10 August 2011
Contents
SAIF Architecture Program – 2011-08-10 Meeting
Return to SAIF Architecture Program Wiki Home Page<br\> Return to SAIF AP Meeting Minutes and Agendas
Meeting Logistics
- Dates: Weekly on Wednesdays
- Time: 10:00 - 11:00 Eastern
- Phone Number: +1 (706) 634-4215 NOTE: This call is using the pilot conference calling number!!!
- Participant Passcode: 124466
- Web Coordinates: https://www2.gotomeeting.com/join/768017802 Meeting ID: 768-017-802
Agenda
- Role Call
- Agenda Review
- Adoption Process Document updates from Project Services (Haddorff) ( HL7AdoptionProcess_draftV10.doc )
- Peer Review comment spreadsheet form adapted from Ballot Comment spreadsheet( Review comments_ArtifactName_draft1.xls )
- Developed by Project Services at suggestion of SAIF AP in conjunction with proposed adoption process
- Peer Review comment spreadsheet form adapted from Ballot Comment spreadsheet( Review comments_ArtifactName_draft1.xls )
- Prepping for the Sept WGM Meeting
- Present what needs to be done for a RASCI chart (which will be a Sept WGM agenda item) (Haddorff)
- SD WG Tuesday Q3 session in San Diego (CDA R3 and SAIF) – invite SAIF AP people to attend that, if interested.
- Recurring Agenda Items
- New Agenda items for San Diego Sept. WGM – Wednesday Q4: 20110914_SAIF_AP_Meeting
- Add the following to the Agenda: SAIF and Sound White paper???
- Pilot Coordination updates (Rick Haddorff)
- Any new Coordination items? (Team)
- Project Schedule progress (Rick Haddorff)
- New Agenda items for San Diego Sept. WGM – Wednesday Q4: 20110914_SAIF_AP_Meeting
- Action item review (see below)
- Next steps
- Please complete the conference calling pilot survey. Next week starts the pilot of the new platform
Action Items to Review
- None to review
Link to the Complete List of Action Items/Issues/Risks (GForge)
Meeting Attendees
X=Present on Call
Facilitator | Austin Kreisler | Note taker(s) | David Hamill |
Attendee | Name | Affiliation | |
X | Austin Kreisler | TSC Chair | |
Brian Pech | Interested Participant | ||
X | David Hamill | HL7 HQ / Program Manager | |
Ed Tripp | Domain Experts SD \ TSC | ||
Gregg Seppala | Product Quality Plan Project | ||
Jane Curry | Tooling | ||
Jim McClay | Emergency Care | ||
John Moehrke | Security Cookbook | ||
John Quinn | HL7 CTO | ||
Lloyd McKenzie | MnM Work Group / SAIF Implementation Guide Pjt | ||
Lorraine Constable | Composite Order Pjt \ OO Behavioral Framework Pjt | ||
Patrick Loyd | OO Work Group / Composite Order Pjt | ||
X | Rick Haddorff | Project Services WG / SAIF Pilot Coordination Pjt | |
Robert Lario | Object Management | ||
X | Pat Van Dyke | EHR WG | |
X | Steve Hufnagel | ArB / SAIF Book Project / SOA | |
Wendy Huang | Implementation Conformance WG | ||
Gary Dickinson | EHR WG | ||
Freida Hall | Project Services WG | ||
Quorum Requirements Met: No |
Minutes
Minutes/Conclusions Reached:
Adoption Process Document updates
Re: the following update in the document:
- Removing the requirement that a Project Scope Statement must be created. Additionally, a paragraph was included explaining instances where a PSS is not required along with Pros/Cons of creating a PSS.
- Austin: Add another line focusing on if another Work Group is adversely impacted by a WG’s internal process, they can petition the TSC and recommend that a Project Scope Statement be created since the proposed process is not internal just to the one WG.
Re: Verbiage focusing on Comment Only is subject to ANSI balloting rules may be incorrect. Project Services will research.
- Austin added the following:
- Con for non-ballot approaches: Runs the risk of not getting people’s attention
- Pro for Comment Only Ballot: Get’s people’s attentions better
- Austin: A lot of Mandated HL7 processes are not part of the WG Health Metrics. Hence, change this to ‘are candidates for WG Health Metrics’ instead of ‘will’
- Regarding the Outstanding Issue indicating that a Work Group should create and maintain a Wiki Page for Informal Ballot Comments, the group agreed that this should be removed, and allow WG’s to decide how they want to do that.
Peer Review comment spreadsheet form adapted from Ballot Comment spreadsheet
- SAIF AP Team should review the document and provide feedback.
- The goal of the spreadsheet is to capture and reconcile comments submitted regarding the proposed process for adoption.
Prepping for the Sept 2011 WGM Meeting
- Rick reviewed the RASCI chart today.
- Once active, may want to do the RASCI chart retroactively
- Rick will work with CDA R3 as the pilot for the RASCI chart and hopefully will have it completed enough to present at the Sept 2011 WGM.
- SAIF and Sound Whitepaper update: It’s dependant on MnM completing work on the artifact definition. Hence there probably won’t be much to report on at the September 2011 WGM.
Gforge Accounts can be requested via:
http://gforge.hl7.org/gf/account/?action=UserAdd
Adjourned 10:55 AM Eastern Time
New Action Items
Rick – Add a line based on Austin’s suggestion about if another Work Group is adversely impacted by a WG’s internal process, they can petition the TSC and recommend that a Project Scope Statement be created since the proposed process is not internal just to the one WG.
Rick – Wordsmith Change to the Adoption Process document ‘defining a Project Scope Statement’ to ‘creating a Project Scope Statement’
Rick – Follow up regarding the Adoption Process verbiage focusing on “Comment Only is subject to ANSI balloting rules” as this may be incorrect.
Rick – Add the Pros/Cons regarding getting people’s attention
Rick – Re: Not all mandated HL7 processes are not part of the WG Health Metrics. Hence, change this to ‘are candidates for WG Health Metrics’ instead of ‘will’
Rick – Remove the Outstanding Issue indicating that a Work Group should create and maintain a Wiki Page for Informal Ballot Comments
Austin/Rick – Have Rick attend a CDA R3 call to bring forward the RASCI work to that project.