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

Difference between revisions of "Conformance Jan 2017 WGM Agenda"

From HL7Wiki
Jump to navigation Jump to search
 
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
  
−
=Proposed Agenda=
+
=Current Agenda=
 
== Sunday ==
 
== Sunday ==
 
<table border="1" width="100%" cellspacing="0">
 
<table border="1" width="100%" cellspacing="0">
Line 43: Line 43:
 
===Admin===
 
===Admin===
 
*Approve agenda
 
*Approve agenda
−
*Approve minutes (Baltimore)
 
 
*Follow-up action items
 
*Follow-up action items
 +
*FHIR tasks
 
*Projects (review)
 
*Projects (review)
 
*Health Metrics
 
*Health Metrics
Line 53: Line 53:
 
*Review gforge tracker items (new, assigned, open, etc.)
 
*Review gforge tracker items (new, assigned, open, etc.)
 
</td>
 
</td>
−
   <td>''TBD''</td>
+
   <td>Rio Grande West</td>
 
   <td>
 
   <td>
 
*Host: Conformance
 
*Host: Conformance
Line 65: Line 65:
  
 
===General Conformance Discussion===
 
===General Conformance Discussion===
−
* Data Type Flavors Discussion
+
* Discuss the current practice of pre-adoption and versioning in respect to the HL7 conformance model. What do we want to do moving forward? Preparing for discussion for InM.
−
* Implementation Guide Template
+
**How to handle HL7 versions you don't expect
−
** Standardized conformance section (Boiler plate language that defines the definitions of conformance the way we want it defined. Included directly or referenced.)
+
**How should people use the V2 Code Tables now?
 
*Pulling out Chapter 2B. Needs a new title: HL7 V2 Conformance Model ?
 
*Pulling out Chapter 2B. Needs a new title: HL7 V2 Conformance Model ?
 
**Higher level of constraint definitions that cross product families
 
**Higher level of constraint definitions that cross product families
 +
* Implementation Guide Template (can go over outline)
 +
** Standardized conformance section (Boiler plate language that defines the definitions of conformance the way we want it defined. Included directly or referenced.)
 
*General V2 Test Cases
 
*General V2 Test Cases
 +
*Frank will show current status for V2 publishing
 +
*Need to know how Conformance WG can be more involved with FHIR conformance
 +
 +
 +
These other topics we will probably postpone
 +
*Data Type Flavors Discussion
 
*Specification of Co-Constraints
 
*Specification of Co-Constraints
 
** Issues associated with giving constraints on items such as Observation (OBX) segments. Every guide author is using different ways of defining the co-constraints.
 
** Issues associated with giving constraints on items such as Observation (OBX) segments. Every guide author is using different ways of defining the co-constraints.
Line 77: Line 85:
 
*Need a best-practices/recommendations for properly using conformance
 
*Need a best-practices/recommendations for properly using conformance
 
**Conformance supports business requirements, business rules determine how to process receiving data
 
**Conformance supports business requirements, business rules determine how to process receiving data
−
**How to handle HL7 versions you don't expect
+
 
  
 
   </td>
 
   </td>
−
   <td>''TBD''</td>
+
   <td>Rio Grande West</td>
 
   <td>
 
   <td>
 
*Host: Conformance
 
*Host: Conformance
Line 97: Line 105:
 
*continue discussion
 
*continue discussion
 
</td>
 
</td>
−
   <td>''TDB''</td>
+
   <td>Rio Grande West</td>
 
   <td>
 
   <td>
 
*Host: Conformance
 
*Host: Conformance
Line 125: Line 133:
 
   <td>
 
   <td>
 
===Conformance within Immunization Space===
 
===Conformance within Immunization Space===
 +
 +
Because of lack of participation from key participants and the lack of pressing items to discuss this meeting will be cancelled for this WGM. We will also not be having this meeting again in May, in anticipation of the lack of participation from US public health in the International meeting. Will look at rescheduling for September 2017 in San Diego (La Jolla!).
  
 
PHER - Immunization
 
PHER - Immunization
Line 135: Line 145:
  
 
</td>
 
</td>
−
<td><i>TBD</i></td>
+
<td><i>Cancelled</i></td>
 
   <td>
 
   <td>
 
Hosting: CGIT<br/>
 
Hosting: CGIT<br/>
Line 146: Line 156:
 
   <th bgcolor="#aef3e7">Q2</th>
 
   <th bgcolor="#aef3e7">Q2</th>
 
   <td>
 
   <td>
 +
 
===Tooling (FHIR, NIST, others?)===
 
===Tooling (FHIR, NIST, others?)===
 
Standing quarter to look at tooling efforts.  
 
Standing quarter to look at tooling efforts.  
Line 151: Line 162:
 
Agenda for demonstrations and discussion will be determined at the start of the quarter based on participants who attend.  
 
Agenda for demonstrations and discussion will be determined at the start of the quarter based on participants who attend.  
 
  </td>
 
  </td>
−
<td><i>TBD</i></td>
+
<td><i>Maverick B</i></td>
 
   <td>
 
   <td>
 
Hosting: CGIT<br/>
 
Hosting: CGIT<br/>
Line 164: Line 175:
 
   <th bgcolor="#aef3e7">Q3</th>
 
   <th bgcolor="#aef3e7">Q3</th>
 
   <td>
 
   <td>
 +
 
===Joint Discussion with InM===
 
===Joint Discussion with InM===
  
Line 228: Line 240:
 
===General Conformance Discussion (final)===
 
===General Conformance Discussion (final)===
 
*Wrap-up and Admin
 
*Wrap-up and Admin
−
**May 2017 WGM agenda planning
+
*May 2017 WGM agenda planning
  
 
</td>
 
</td>
−
   <td><i>TBD</i></td>
+
   <td>Maverick B</td>
 
   <td>
 
   <td>
 
Hosting: CGIT<br/>
 
Hosting: CGIT<br/>
Line 263: Line 275:
  
 
</td>
 
</td>
−
   <td><i>TBD</i></td>
+
   <td><i>Pecos</i></td>
 
   <td>Hosting: Vocab</td>
 
   <td>Hosting: Vocab</td>
 
  </tr>
 
  </tr>
Line 269: Line 281:
 
   <th bgcolor="#aef3e7">Q2</th>
 
   <th bgcolor="#aef3e7">Q2</th>
 
   <td>
 
   <td>
 +
 
===Vocabulary===
 
===Vocabulary===
 
*Vocabulary [http://wiki.hl7.org/index.php?title=Binding_Syntax Binding Syntax: Requirements]
 
*Vocabulary [http://wiki.hl7.org/index.php?title=Binding_Syntax Binding Syntax: Requirements]
 
</td>
 
</td>
−
   <td><i>TBD</i></td>
+
   <td><i>Pecos</i></td>
 
   <td>Hosting: Vocab</td>
 
   <td>Hosting: Vocab</td>
 
  </tr>
 
  </tr>
Line 281: Line 294:
 
   <th bgcolor="#aef3e7">Q3</th>
 
   <th bgcolor="#aef3e7">Q3</th>
 
   <td>
 
   <td>
 +
 
===Vocabulary===
 
===Vocabulary===
 +
Conformance Co-Chairs will not be able to make this joint meeting due to other conflicts.
 +
 
</td>
 
</td>
−
   <td><i>TBD</i></td>
+
   <td>Rio Grande Center </td>
 
   <td>Hosting: Vocab</td>
 
   <td>Hosting: Vocab</td>
 
  </tr>
 
  </tr>

Latest revision as of 15:49, 16 January 2017

Current Agenda

Sunday

Quarter Agenda Room Responsibilities
Q1 not meeting
Q2 not meeting
Q3 not meeting
Q4 not meeting

Monday

Quarter Agenda Room Responsibilities
Q1

Admin

  • Approve agenda
  • Follow-up action items
  • FHIR tasks
  • Projects (review)
  • Health Metrics
  • Review and approve SWOT
  • Review and approve DMP
  • Review and approve Mission & Charter
  • Review and approve 3 year plan
  • Review gforge tracker items (new, assigned, open, etc.)
 Rio Grande West
  • Host: Conformance
  • Chair: Nathan
  • Scribe: Rob
Q2

General Conformance Discussion

  • Discuss the current practice of pre-adoption and versioning in respect to the HL7 conformance model. What do we want to do moving forward? Preparing for discussion for InM.
    • How to handle HL7 versions you don't expect
    • How should people use the V2 Code Tables now?
  • Pulling out Chapter 2B. Needs a new title: HL7 V2 Conformance Model ?
    • Higher level of constraint definitions that cross product families
  • Implementation Guide Template (can go over outline)
    • Standardized conformance section (Boiler plate language that defines the definitions of conformance the way we want it defined. Included directly or referenced.)
  • General V2 Test Cases
  • Frank will show current status for V2 publishing
  • Need to know how Conformance WG can be more involved with FHIR conformance


These other topics we will probably postpone

  • Data Type Flavors Discussion
  • Specification of Co-Constraints
    • Issues associated with giving constraints on items such as Observation (OBX) segments. Every guide author is using different ways of defining the co-constraints.
    • Discuss ideas about how to standardize the expression of these co-constraints.
    • Asking for feedback in regards to how this is done in other standards such as V3, FHIR, etc.
  • Need a best-practices/recommendations for properly using conformance
    • Conformance supports business requirements, business rules determine how to process receiving data


 Rio Grande West
  • Host: Conformance
  • Chair: Rob
  • Scribe: Nathan
Lunch
Q3

General Conformance Discussion

  • continue discussion
 Rio Grande West
  • Host: Conformance
  • Chair: Rob
  • Scribe: Nathan
Q4 not meeting

Tuesday

Quarter Agenda Room Responsibilities
Q1

Conformance within Immunization Space

Because of lack of participation from key participants and the lack of pressing items to discuss this meeting will be cancelled for this WGM. We will also not be having this meeting again in May, in anticipation of the lack of participation from US public health in the International meeting. Will look at rescheduling for September 2017 in San Diego (La Jolla!).

PHER - Immunization

  • Overview of Immunization Tooling (NIST, AART) : Rob Snelick / Nathan Bunker
  • Update on Implementation Guide : Craig Newman
  • Acknowledgement Best Practices and Testing : Eric Larson / Nathan Bunker
  • Functional Requirements and Testing : Eric Larson
  • Update/Planning on CDSi Testing : Eric Larson / Rob Snelick
  • Data Quality Issues and Testing : Nathan Bunker / Rob Snelick
 Cancelled

Hosting: CGIT
Joining: PHER
Chair: Nathan
Scribe: Rob

Q2

Tooling (FHIR, NIST, others?)

Standing quarter to look at tooling efforts.

Agenda for demonstrations and discussion will be determined at the start of the quarter based on participants who attend.

Maverick B

Hosting: CGIT
Chair: Rob
Scribe: Nathan

Lunch
Q3

Joint Discussion with InM

Items that need to be discussed:

  • Follow up on the proposal to remove concept of "original mode".
  • Discuss backwards compatibility, what is the standard
  • How binding is the conformance on length? Especially on older versions that have statements on length but which may or may not be binding.
  • How should the current conformance model be used on older versions and profiles.
  • Policy on pre-adoption, best-practices (likely: don't do it, go to the latest version), data types, vocabulary.
  • Should evaluate implementation aspects of versions of standards (systems can get locked into versions and can't support newer versions)
 TBD

Hosting: InM

Q4 not meeting

Wednesday

Quarter Agenda Room Responsibilities
Q1 not meeting - Conformance Tutorial
Q2 not meeting - Conformance Tutorial
Lunch
Q3

FHIR discussions

  • Implementation Guide
  • Conformance Rules
Other items...		 TBD

Hosting: Conformance
Joining: FHIR-I, Templates
Chair: Frank
Scribe: Nathan

Q4

General Conformance Discussion (final)

  • Wrap-up and Admin
  • May 2017 WGM agenda planning
 Maverick B

Hosting: CGIT
Chair: Rob
Scribe: Nathan

Thursday

Quarter Agenda Room Responsibilities
Q1

Vocabulary

  • Terminology Quality Assurance
  • Tables Project

Items that can be discussed Thursday AM

  • Table 0163 and 0550.
  • Adding new codes to HL7 tables (what code system to use, what is the process)
  • How to use the new code systems (hl7 table project)
 Pecos Hosting: Vocab
Q2

Vocabulary

 Pecos Hosting: Vocab
Lunch
Q3

Vocabulary

Conformance Co-Chairs will not be able to make this joint meeting due to other conflicts.

Rio Grande Center Hosting: Vocab
Q4 not meeting

Friday

Quarter Agenda Room Responsibilities
Q1 not meeting
Q1 not meeting

Quarter Times

Quarter Time
Q1 9:00 AM - 10:30 AM
Q2 11:00 AM - 12:30 PM
Q3 1:45 PM - 3:00 PM
Q4 3:30 PM - 5:00 PM
Retrieved from "https://wiki.hl7.org/w/index.php?title=Conformance_Jan_2017_WGM_Agenda&oldid=131422"