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
Line 97: Line 97:
 
*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>
Line 180: Line 181:
 
  </td>
 
  </td>
 
   <td>CGIT</td>
 
   <td>CGIT</td>
−
   <td>PHER</td>
+
   <td></td>
 
   <td>Rob</td>
 
   <td>Rob</td>
 
   <td>Nathan</td>
 
   <td>Nathan</td>
Line 192: Line 193:
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td>[[Image:Technical_med.gif|right|Technical Meeting]]</td>
 
   <td></td>
 
   <td></td>
−
   <td>Rob Snelick is putting together agenda:
+
   <td>Items that need to be discussed:
−
* Clarifications on original ack mode vs enhanced ack mode (particularly the defaults). Discuss the potential conflict with MSH definition and profiling.
+
* Follow up on the proposal to remove concept of "original mode".  
−
* 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.  
+
* 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)
 
</td>
 
</td>
 
   <td>InM</td>
 
   <td>InM</td>

Revision as of 20:38, 21 September 2016

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
Technical Meeting
 Admin
  • Approve agenda
  • Approve minutes (Baltimore)
  • Follow-up action items
  • 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.)
 CGIT   Nathan Rob
Q2
Technical Meeting
 General Conformance Discussion

Discussion Items:

  • Data Type Flavors Discussion
  • Implementation Guide Template
    • Standardized conformance section (Boiler plate language that defines the definitions of conformance the way we want it defined. Included directly or referenced.)
  • Pulling out Chapter 2B. Needs a new title: HL7 V2 Conformance Model ?
    • Higher level of constraint definitions that cross product families
  • General V2 Test Cases
  • 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
    • How to handle HL7 versions you don't expect
 CGIT Rob Nathan
Lunch
PM Q3
Technical Meeting
 General Conformance Discussion

continue

CGIT   Nathan Rob
Q4
Technical Meeting
 General Conformance Discussion continue CGIT Rob Nathan
Day Time   Icon Ver. Event Host joining Chair Scribe
Tuesday AM Q1
Technical Meeting
 Conformance within Immunization Space 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
 CGIT PHER Nathan Rob
Q2
Technical Meeting
 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.

CGIT Rob Nathan
Lunch
PM Q3
Technical Meeting
 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)
 InM    
Q4
Technical Meeting
 General Conformance Discussion (cont)

Additional items that could be discussed:

  • Data Type Flavors
  • Any other PHER conformance issues

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 - Ioana 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 Nathan
Q4
Technical Meeting
 General Conformance Discussion (final)
  • Continuation of Conformance Tutorial Review
  • Continuation of Data Type Flavors Discussion
  • Wrap-up and Admin
    • January 2017 WGM agenda planning
 CGIT - Rob Nathan
Day Time   Icon Ver. Event Host joining Attend Scribe
Thursday AM Q1
Technical Meeting
 Vocab
  • 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)
 Vocab CGIT Nathan, Frank, Rob -
Q2
Business Meeting
 Vocab Vocab CGIT Rob, Frank -
Lunch
Q3 not meeting
Q4 not meeting
Day Time   Icon Ver. Event Host joining Chair Scribe
Friday AM Q1 not meeting
Q2 not meeting
Retrieved from "https://wiki.hl7.org/w/index.php?title=Conformance_Jan_2017_WGM_Agenda&oldid=126234"