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

Difference between revisions of "CGITWG Jan 2016 WGM Agenda"

From HL7Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 91: Line 91:
 
*Wait until moving to v2+ before making changes. Need to formalize the position statement so we can elevate it up to the steering committee.  
 
*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.  
 
*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
 
Test Data Categorizations
 
*Testing associated to specific test cases. Need to review the categories.  
 
*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 171: Line 175:
 
**Test Case Authoring and Management Tool (TCAMT) - Introduction and Demo
 
**Test Case Authoring and Management Tool (TCAMT) - Introduction and Demo
 
*Other Profiling Tools
 
*Other Profiling Tools
**Ioana suggested this
+
**Model-Driven Approach (MDHT, MDHT)
 
*AEGIS
 
*AEGIS
 
*FHIR
 
*FHIR
**FORGE
+
** [http://fhir.furore.com/forge Furore FORGE]
 
</td>
 
</td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
Line 188: Line 192:
 
<ul>
 
<ul>
 
       <li>Discuss strategy to provide input to FHIR on conformance. </li>
 
       <li>Discuss strategy to provide input to FHIR on conformance. </li>
       <li>discuss generic conformance documents</li>
+
       <li>discuss generic conformance format that may be applicable to any HL7 product line.</li>
 
       </ul>
 
       </ul>
 
</td>
 
</td>
Line 203: Line 207:
 
   <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>v2.9</td>
+
   <td></td>
   <td>Future of HL7 V2:
+
   <td>???? Cancelling ????</td>
*Presentation from Frank on improvements for HL7 v2+, documenting HL7 v2 going forward
 
*Discuss creating a separate chapter for Conformance
 
</td>
 
 
   <td>InM</td>
 
   <td>InM</td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
   <td>???? Cancelling ????</td>
+
   <td></td>
 
   <td>&nbsp;</td>
 
   <td>&nbsp;</td>
 
  </tr>
 
  </tr>

Latest revision as of 21:32, 14 December 2015


Proposed CGIT Agenda for the January 2016 Working Group Meeting in Orlando, FL, USA

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

Open Issues

Chairing and scribing resources to be confirmed.

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 (San Antonio, Paris)
  • review and approve SWOT
  • review and approve DMP
  • review and approve Mission & Charter
  • conformance facilitator: establish a fixed quarter for facilitators to attend
  • follow-up action items
  • projects (review)
    • close RCnL Project
    • review timelines and status
  • proposal to change name of CGIT to Conformance
  • Documenting Local Implementation Status
CGIT   Frank Rob
Q2
Technical Meeting
Conformance Chapter 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
CGIT - - -
Lunch
PM Q3
Technical Meeting
Documenting 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)
CGIT   Frank Rob
Q4
Technical Meeting
Discussion Overflow

Continuation of Q2 and Q3 discussions

Additional topics if there is time:

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.

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??
CGIT Rob Frank
Day Time   Icon Ver. Event Host joining Chair Scribe
Tuesday AM Q1
Technical Meeting
Conformance Tools
  • 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
    • Model-Driven Approach (MDHT, MDHT)
  • AEGIS
  • FHIR
CGIT Rob Frank
Q2
Technical Meeting
Conformance Strategy Discussion of Strategy for Conformance in FHIR, V3, etc.
  • 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
???? Cancelling ???? InM    
Q4
Technical Meeting
Wrap-up and Admin
  • May 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
Technical Meeting
FHIR Continuation of Q3 CGIT FHIR, Templates Frank Frank
Day Time   Icon Ver. Event Host joining Attend Scribe
Thursday AM Q1
Technical Meeting
V2/V3/FHIR Continuation of Discussions from Weekly Calls Vocab CGIT Nathan, Frank, Rob -
Q2
Business Meeting
Tooling
Vocab
  • Joint w/Vocab: continuation of Q1 (Tables Project)
Tooling
Vocab
CGIT Rob, Frank -
Lunch
PM Q3 not meeting
Q4 not meeting
Day Time   Icon Ver. Event Host joining Chair Scribe
Friday AM Q1 not meeting
Q2 not meeting