This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20160906 arb minutes"
Jump to navigation
Jump to search
m (→Minutes) |
m (→Minutes) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 38: | Line 38: | ||
|- | |- | ||
| width="10%" colspan="1" align="right"|'''Facilitator''' | | width="10%" colspan="1" align="right"|'''Facilitator''' | ||
| − | | width="35%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]] | + | | width="35%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]] |
| width="10%" colspan="1" align="right"|'''Note taker(s)''' | | width="10%" colspan="1" align="right"|'''Note taker(s)''' | ||
| − | | width="30%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]] | + | | width="30%" colspan="1" align="left"|[[User:Ajulian | Julian, Tony]] |
|- | |- | ||
| border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"| | | border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"| | ||
| Line 48: | Line 48: | ||
|colspan="2"|'''Affiliation''' | |colspan="2"|'''Affiliation''' | ||
|- | |- | ||
| − | | | + | |X||Bond,Andy |
|colspan="2"|NEHTA | |colspan="2"|NEHTA | ||
|- | |- | ||
| − | | | + | |X||[[User:Lconstab |Constable, Lorraine]] |
|colspan="2"|Constable Consulting Inc. | |colspan="2"|Constable Consulting Inc. | ||
|- | |- | ||
| − | | | + | |R||Dagnall, Bo |
|colspan="2"|HP Enterprise Services | |colspan="2"|HP Enterprise Services | ||
|- | |- | ||
| Line 60: | Line 60: | ||
|colspan="2"| ????? | |colspan="2"| ????? | ||
|- | |- | ||
| − | | | + | |X||[[User:Interopguy | Hyland, Mario]] |
|colspan="2"| AEGIS | |colspan="2"| AEGIS | ||
|- | |- | ||
| − | | | + | |X||[[User:Ajulian | Julian, Tony]] |
|colspan="2"|Mayo Clinic | |colspan="2"|Mayo Clinic | ||
|- | |- | ||
| − | | | + | |R||Knapp, Paul |
|colspan="2"| Pknapp Consulting | |colspan="2"| Pknapp Consulting | ||
|- | |- | ||
| − | | | + | |X||Kubick, Wayne |
|colspan="2"|HL7 CTO | |colspan="2"|HL7 CTO | ||
|- | |- | ||
| Line 75: | Line 75: | ||
|colspan="2"| ICode Solutions | |colspan="2"| ICode Solutions | ||
|- | |- | ||
| − | | | + | |R||[[User:Clynchmd | Lynch, Cecil]] |
|colspan="2"|Accenture | |colspan="2"|Accenture | ||
|- | |- | ||
| − | | | + | |R||Milosevic, Zoran |
|colspan="2"|Deontik Pty Ltd | |colspan="2"|Deontik Pty Ltd | ||
|- | |- | ||
| Line 88: | Line 88: | ||
|.|| Nelson, Dale | |.|| Nelson, Dale | ||
|colspan="2"| Accenture | |colspan="2"| Accenture | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|.|| | |.|| | ||
| Line 113: | Line 110: | ||
==Minutes== | ==Minutes== | ||
| − | #*A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications. | + | #Methodology |
| − | #*Lorraine - Implementation Guide writes conformance statements to conform to a specific implementation profile. | + | #*Definition of "Guidance" product |
| − | #*Andy S: Implementation Guide describes conformance to a standard(s). | + | #**[[20160816_arb_minutes | August 16 Minutes]] |
| − | #*Andy B: not the same as a conformance profile | + | #**A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications. |
| − | #*Lorraine: Could conformance profile appear in an Implementation Guide? | + | #**Lorraine - Implementation Guide writes conformance statements to conform to a specific implementation profile. |
| − | #*Andy B: IG should not be aligned with conformance document - does not line up with ISO conformance. Conformance profile could be part of an Implementation Guide. | + | #**Andy S: Implementation Guide describes conformance to a standard(s). |
| − | #*Mario: Guidance document may be version agnostic. | + | #**Andy B: not the same as a conformance profile |
| − | #*Wayne: Define Implementation Guide first. | + | #**Lorraine: Could conformance profile appear in an Implementation Guide? |
| − | #*Andy B: not refer to them together. | + | #**Andy B: IG should not be aligned with conformance document - does not line up with ISO conformance. Conformance profile could be part of an Implementation Guide. |
| − | #*Marion: Lorraine's thought - guidance document talks about more than implementation. | + | #**Mario: Guidance document may be version agnostic. |
| − | #*Lorraine: White papers, informative, cookbooks may describe implementation guidance. Consolidated CDA companion guide is about guidance, but is not an Implementation Guide even though Implementation Guide is in its full title. Historical error. | + | #**Wayne: Define Implementation Guide first. |
| − | #* Andy B: Designed to be Normative track Implementation Guide. | + | #**Andy B: not refer to them together. |
| − | #*A Guidance document is a type of informative document that describes principles, best practices, and general advice but is not sufficient to achieve the conformant implementation of one or more standards. | + | #**Marion: Lorraine's thought - guidance document talks about more than implementation. |
| + | #**Lorraine: White papers, informative, cookbooks may describe implementation guidance. Consolidated CDA companion guide is about guidance, but is not an Implementation Guide even though Implementation Guide is in its full title. Historical error. | ||
| + | #** Andy B: Designed to be Normative track Implementation Guide. | ||
| + | #*'''Definition:''' | ||
| + | #**A Guidance document is a type of informative document that describes principles, best practices, and general advice but is not sufficient to achieve the conformant implementation of one or more standards. | ||
#**'''Motion to accept the above'''(Andy S/Lorraine) | #**'''Motion to accept the above'''(Andy S/Lorraine) | ||
#**'''Vote''' (5-0-0) | #**'''Vote''' (5-0-0) | ||
#*Question for TSC: On re-ballot of existing documents do we rename them , even if reaffirmation? | #*Question for TSC: On re-ballot of existing documents do we rename them , even if reaffirmation? | ||
| + | #Management | ||
| + | #*[[2016_ARB_Baltimore_WGM |Baltimore Planning]] reviewed | ||
| + | #*[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FMission_charter.docx Mission and Charter] was again reviewed. | ||
| + | #Other business and planning | ||
| + | #* The following will be reviewed on the next call. | ||
| + | ##[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FMission_charter.docx Mission and Charter Review] | ||
| + | ##[http://gforge.hl7.org/gf/project/arbgeneral/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Ftrunk%2FARB%2520DMP%2520v6%2520.docx Decision Making Procedures review] | ||
| + | #Adjournment | ||
| + | #* Meeting adjourned at 5:08 PM Eastern | ||
| + | |||
| + | [[User:Ajulian|Tony Julian]] ([[User talk:Ajulian|talk]]) 17:11, 6 September 2016 (EDT) | ||
[[Category:2016 Arb Minutes]] | [[Category:2016 Arb Minutes]] | ||
Latest revision as of 21:11, 6 September 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.
- Join the meeting:
- Join the online meeting: Online Meeting Link:https://join.freeconferencecall.com/arb97
- Online Meeting ID:arb97
- If you cant use voip then capture the PIN from the screen for the above action, then
- Dial into the conference: Dial-in Number:(605) 472-5556 - United States
- enter the access code 332183
- enter the pin.
- International Dial-in Numbers:https://www.freeconferencecall.com/wall/arb97/#international
- Weekly conference call.
- For 24/7 customer service please call (844) 844-1322.
Agenda
- Call to order
- Roll Call
- Approval of Agenda and Minutes
- Methodology
- Definition of "Guidance" product
- August 16 Minutes
- Management
- Governance
- Other business and planning
- Adjournment
Meeting Information
| HL7 ArB Work Group Meeting Minutes Location: Telcon |
Date: 20160906 Time: 4:00pm U.S. Eastern | |||
| Facilitator | Julian, Tony | Note taker(s) | Julian, Tony | |
| Attendee | Name | Affiliation | ||
| X | Bond,Andy | NEHTA | ||
| X | Constable, Lorraine | Constable Consulting Inc. | ||
| R | Dagnall, Bo | HP Enterprise Services | ||
| . | Hufnagel, Steve | ????? | ||
| X | Hyland, Mario | AEGIS | ||
| X | Julian, Tony | Mayo Clinic | ||
| R | Knapp, Paul | Pknapp Consulting | ||
| X | Kubick, Wayne | HL7 CTO | ||
| . | Loyd, Patrick | ICode Solutions | ||
| R | Lynch, Cecil | Accenture | ||
| R | Milosevic, Zoran | Deontik Pty Ltd | ||
| . | Stechishin,Andy | CANA Software and Service Ltd. | ||
| Guests | ||||
| . | Nelson, Dale | Accenture | ||
| . | ||||
| Legend | ||||
| X | Present | |||
| . | Absent | |||
| R | Regrets | |||
| Quorum Requirements (Co-chair + 3) Met: Yes | ||||
Minutes
- Methodology
- Definition of "Guidance" product
- August 16 Minutes
- A Guidance is a type of informative document that describes principles, best practices, and general advice but is not directly related to implementation of one or more specifications.
- Lorraine - Implementation Guide writes conformance statements to conform to a specific implementation profile.
- Andy S: Implementation Guide describes conformance to a standard(s).
- Andy B: not the same as a conformance profile
- Lorraine: Could conformance profile appear in an Implementation Guide?
- Andy B: IG should not be aligned with conformance document - does not line up with ISO conformance. Conformance profile could be part of an Implementation Guide.
- Mario: Guidance document may be version agnostic.
- Wayne: Define Implementation Guide first.
- Andy B: not refer to them together.
- Marion: Lorraine's thought - guidance document talks about more than implementation.
- Lorraine: White papers, informative, cookbooks may describe implementation guidance. Consolidated CDA companion guide is about guidance, but is not an Implementation Guide even though Implementation Guide is in its full title. Historical error.
- Andy B: Designed to be Normative track Implementation Guide.
- Definition:
- A Guidance document is a type of informative document that describes principles, best practices, and general advice but is not sufficient to achieve the conformant implementation of one or more standards.
- Motion to accept the above(Andy S/Lorraine)
- Vote (5-0-0)
- Question for TSC: On re-ballot of existing documents do we rename them , even if reaffirmation?
- Definition of "Guidance" product
- Management
- Baltimore Planning reviewed
- Mission and Charter was again reviewed.
- Other business and planning
- The following will be reviewed on the next call.
- Adjournment
- Meeting adjourned at 5:08 PM Eastern
Tony Julian (talk) 17:11, 6 September 2016 (EDT)
