This wiki has undergone a migration to Confluence found Here

Difference between revisions of "CGITWG May 2016 WGM Agenda"

From HL7Wiki
Jump to navigation Jump to search
m
 
(6 intermediate revisions by the same user not shown)
Line 79: Line 79:
 
   <td>Q2</td>
 
   <td>Q2</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
   <td>Conformance Chapter</td>
+
   <td>General Conformance Discussion</td>
 
   <td>
 
   <td>
Discussion Items(s) TBD
+
    V2 Basic Test Cases
 +
    *Discussion on how to define basic HL7 v2 basic test cases for verifying support for basic encoding in Chapter 2
 +
 
 +
    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. 
  
placeholder below:
 
  
Moving the Conformance chapter out of the HL7 v2 Standard
 
*Need to continue working on the position statement pros/cons
 
*Wait until moving to v2+ before making changes. Need to formalize the position statement so we can elevate it up to the steering committee.
 
*Rob will clean up the position statement, based on the notes from the September meeting, so we can have a formal review.
 
*Discuss revising the message profile/xml/json representation based on best practices developed by NIST
 
  
Test Data Categorizations
 
*Testing associated to specific test cases. Need to review the categories.
 
  
V2 Basic Test Cases
 
*Discussion on how to define basic HL7 v2 basic test cases for verifying support for basic encoding in Chapter 2
 
 
</td>
 
</td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
Line 109: Line 105:
 
   <td>Q3</td>
 
   <td>Q3</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
   <td>Documenting</td>
+
   <td>General Conformance Discussion (cont).</td>
 
   <td>
 
   <td>
Discussion continues (TBD)
+
  HL7 v2 Delete "" Discussion
 
 
  
Request for Feedback on Project to Document HL7 v2 Interfaces
+
  HL7 v2 Data Type Flavors Standardization
*Present and Discuss Effort to Profile and Document current HL7 V2 Interfaces (e.g. Immunization Information Systems)
+
 
</td>
 
</td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
Line 127: Line 122:
  
 
[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
[[Image:Technical_med.gif|right|Technical Meeting]]</td>
<td>Discussion Overflow</td>
+
<td>General Conformance Discussion (cont)</td>
   <td>
+
   <td><i>Discussion continues (TBD)</i>
<i>
 
Discussion continues (TBD)
 
 
 
 
 
 
 
Continuation of Q2 and Q3 discussions</i>
 
  
Additional topics if there is time:
+
  HL7 v2 Delete "" Discussion (cont.)
  
Specification of Co-Constraints
+
  HL7 v2 Data Type Flavors Standardization (cont.)
*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.  
 
  
v2.9 Proposals (Parked proposals for waiting for v2+):
 
*Message Profile Identifiers (Managing multiple versions-OIDs)
 
*Managing Value Set OIDs (How to specify in MSH.21)
 
*Harmonized Data Type Flavors in Profiling (e.g., TS_1, TS_2, etc.)
 
*Specifying explicit conformance statements in the base standard and IGs
 
*Replace CWE/CNE/etc. with simple and complex coded element??
 
 
</td>
 
</td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
Line 218: Line 199:
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td></td>
 
   <td></td>
   <td>Need to connect with InM to see if we will meet. </td>
+
   <td><i>Need to connect with InM to see if we will meet.</i></td>
 
   <td>InM</td>
 
   <td>InM</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
Line 281: Line 262:
 
  <tr>
 
  <tr>
 
   <td>Q4</td>
 
   <td>Q4</td>
   <td></td>
+
   <td colspan="7"><i>not meeting</i></td>
  <td></td>
 
  <td></td>
 
  <td></td>
 
  <td></td>
 
  <td></td>
 
  <td></td>
 
 
</tr>
 
</tr>
  
Line 309: Line 284:
 
   <td>Q1</td>
 
   <td>Q1</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
   <td>V2/V3/FHIR</td>
+
   <td>Vocab</td>
 
   <td>Continuation of Discussions from Weekly Calls
 
   <td>Continuation of Discussions from Weekly Calls
 
*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]
Line 322: Line 297:
 
   <td>Q2</td>
 
   <td>Q2</td>
 
   <td>[[Image:business_med.gif|right|Business Meeting]]</td>
 
   <td>[[Image:business_med.gif|right|Business Meeting]]</td>
   <td>Tooling<br/>Vocab</td>
+
   <td>Vocab</td>
 
   <td>
 
   <td>
*Joint w/Vocab: continuation of Q1 (Tables Project)
+
Continuation from Q1
 +
*Vocabulary [http://wiki.hl7.org/index.php?title=Binding_Syntax Binding Syntax: Requirements]
 +
*Terminology Quality Assurance
 +
*Tables Project
 
</td>
 
</td>
   <td>Tooling<br/>Vocab</td>
+
   <td>Vocab</td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
 
   <td>Rob, Frank</td>
 
   <td>Rob, Frank</td>
Line 338: Line 316:
 
   <td>Q3</td>
 
   <td>Q3</td>
 
   <td>[[Image:business_med.gif|right|Business Meeting]]</td>
 
   <td>[[Image:business_med.gif|right|Business Meeting]]</td>
   <td>Tooling<br/>Vocab</td>
+
   <td>Vocab</td>
 
   <td>
 
   <td>
*Joint w/Vocab: continuation of Q1 (Tables Project)
+
*Continuation of Q2 (Tables Project)
 
</td>
 
</td>
   <td>Tooling<br/>Vocab</td>
+
   <td>Vocab</td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
 
   <td>Frank</td>
 
   <td>Frank</td>
Line 378: Line 356:
 
  </tr>
 
  </tr>
 
</table>
 
</table>
 +
 +
 +
== Parking Lot ==
 +
Discussion Items(s) TBD
 +
 +
Conformance usage to override required message elements in the base specification (Resolved on list serve need to document outcome for wider community.)
 +
 +
Moving the Conformance chapter out of the HL7 v2 Standard
 +
*Need to continue working on the position statement pros/cons
 +
*Wait until moving to v2+ before making changes. Need to formalize the position statement so we can elevate it up to the steering committee.
 +
*Rob will clean up the position statement, based on the notes from the September meeting, so we can have a formal review.
 +
*Discuss revising the message profile/xml/json representation based on best practices developed by NIST
 +
 +
Test Data Categorizations
 +
*Testing associated to specific test cases. Need to review the categories.
 +
 +
 +
Request for Feedback on Project to Document HL7 v2 Interfaces
 +
*Present and Discuss Effort to Profile and Document current HL7 V2 Interfaces (e.g. Immunization Information Systems)
 +
 +
v2.9 Proposals (Parked proposals for waiting for v2+):
 +
*Message Profile Identifiers (Managing multiple versions-OIDs)
 +
*Managing Value Set OIDs (How to specify in MSH.21)
 +
*Harmonized Data Type Flavors in Profiling (e.g., TS_1, TS_2, etc.)
 +
*Specifying explicit conformance statements in the base standard and IGs
 +
*Replace CWE/CNE/etc. with simple and complex coded element??

Latest revision as of 20:34, 18 April 2016


Proposed CGIT Agenda for the May 2016 Working Group Meeting in Montreal, Quebec, Canada

Return to Conformance and Guidance for Implementation/Testing#Working Group Meeting Agendas and Minutes page.

Open Issues

  • Not complete yet
Day Time Icon Ver. Event Host joining Chair Scribe
Sunday AM Q1 not meeting
Q2 not meeting
PM Q3 not meeting
Q4 not meeting
Day Time   Icon Ver. Event Host joining Chair Scribe
Monday AM Q1
Business Meeting
Admin
  • approve agenda
  • approve minutes (Orlando)
  • conformance facilitator: establish a fixed quarter for facilitators to attend
  • follow-up action items
  • projects (review)
CGIT   Frank Rob
Q2
Technical Meeting
General Conformance Discussion
    V2 Basic Test Cases
    *Discussion on how to define basic HL7 v2 basic test cases for verifying support for basic encoding in Chapter 2
    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.  



CGIT - - -
Lunch
PM Q3
Technical Meeting
General Conformance Discussion (cont).
  HL7 v2 Delete "" Discussion
  HL7 v2 Data Type Flavors Standardization

CGIT   Frank Rob
Q4
Technical Meeting
General Conformance Discussion (cont) Discussion continues (TBD)
  HL7 v2 Delete "" Discussion (cont.)
  HL7 v2 Data Type Flavors Standardization (cont.)

CGIT Rob Frank
Day Time   Icon Ver. Event Host joining Chair Scribe
Tuesday AM Q1
Technical Meeting
Conformance Tools

Items might include:

  • AEGIS
  • FHIR
  • Update on Message Workbench Status
  • NIST Conformance Tools - Open Discussion
  • NIST Conformance and Testing Productivity Tools
    • Implementation Guide Authoring and Management Tool (IGAMT) Update and Demo
    • Test Case Authoring and Management Tool (TCAMT) - Introduction and Demo
  • Other Profiling Tools
CGIT Rob Frank
Q2
Technical Meeting
Conformance Strategy

Discussion of Unified Strategy for Conformance

  • Discuss strategy to provide input to FHIR on conformance.
  • Discuss generic conformance format that may be applicable to any HL7 product line.
CGIT Ioana Frank
Lunch
PM Q3
Technical Meeting
Need to connect with InM to see if we will meet. InM    
Q4
Technical Meeting
Wrap-up and Admin
  • September 2016 WGM agenda planning
  • Continuation of any topics
CGIT - Frank Nathan
Day Time   Icon Ver. Event Host joining Chair Scribe
Wednesday AM Q1 not meeting
Q2 not meeting
Lunch
PM Q3
Technical Meeting
FHIR FHIR discussions
  • Implementation Guide
  • Conformance Rules
Other items...
CGIT FHIR, Templates, Vocab Frank Frank
Q4 not meeting
Day Time   Icon Ver. Event Host joining Attend Scribe
Thursday AM Q1
Technical Meeting
Vocab Continuation of Discussions from Weekly Calls Vocab CGIT Nathan, Frank, Rob -
Q2
Business Meeting
Vocab

Continuation from Q1

Vocab CGIT Rob, Frank -
Lunch
PM Q3
Business Meeting
Vocab
  • Continuation of Q2 (Tables Project)
Vocab CGIT Frank -
Q4 not meeting
Day Time   Icon Ver. Event Host joining Chair Scribe
Friday AM Q1 not meeting
Q2 not meeting


Parking Lot

Discussion Items(s) TBD

Conformance usage to override required message elements in the base specification (Resolved on list serve need to document outcome for wider community.)

Moving the Conformance chapter out of the HL7 v2 Standard

  • Need to continue working on the position statement pros/cons
  • Wait until moving to v2+ before making changes. Need to formalize the position statement so we can elevate it up to the steering committee.
  • Rob will clean up the position statement, based on the notes from the September meeting, so we can have a formal review.
  • Discuss revising the message profile/xml/json representation based on best practices developed by NIST

Test Data Categorizations

  • Testing associated to specific test cases. Need to review the categories.


Request for Feedback on Project to Document HL7 v2 Interfaces

  • Present and Discuss Effort to Profile and Document current HL7 V2 Interfaces (e.g. Immunization Information Systems)

v2.9 Proposals (Parked proposals for waiting for v2+):

  • Message Profile Identifiers (Managing multiple versions-OIDs)
  • Managing Value Set OIDs (How to specify in MSH.21)
  • Harmonized Data Type Flavors in Profiling (e.g., TS_1, TS_2, etc.)
  • Specifying explicit conformance statements in the base standard and IGs
  • Replace CWE/CNE/etc. with simple and complex coded element??