This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CGITWG May 2016 WGM Agenda"
Jump to navigation
Jump to search
Line 100: | Line 100: | ||
<td> | <td> | ||
HL7 v2 Delete "" Discussion | HL7 v2 Delete "" Discussion | ||
+ | |||
+ | HL7 v2 Data Type Flavors Standardization | ||
+ | |||
</td> | </td> | ||
<td>CGIT</td> | <td>CGIT</td> | ||
Line 111: | Line 114: | ||
[[Image:Technical_med.gif|right|Technical Meeting]]</td> | [[Image:Technical_med.gif|right|Technical Meeting]]</td> | ||
− | <td>Discussion | + | <td>General Conformance Discussion (cont)</td> |
<td> | <td> | ||
− | <i> | + | <i>Discussion continues (TBD)</i> |
− | Discussion continues (TBD) | ||
− | |||
− | |||
− | + | HL7 v2 Delete "" Discussion (cont.) | |
− | + | HL7 v2 Data Type Flavors Standardization (cont.) | |
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</td> | </td> | ||
<td>CGIT</td> | <td>CGIT</td> | ||
Line 387: | Line 377: | ||
Request for Feedback on Project to Document HL7 v2 Interfaces | 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) | *Present and Discuss Effort to Profile and Document current HL7 V2 Interfaces (e.g. Immunization Information Systems) | ||
+ | |||
+ | |||
+ | 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?? |
Revision as of 20:24, 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 | Admin |
|
CGIT | Frank | Rob | ||
Q2 | General Conformance Discussion |
|
CGIT | - | - | - | |||
Lunch | |||||||||
PM | Q3 | General Conformance Discussion (cont). |
HL7 v2 Delete "" Discussion HL7 v2 Data Type Flavors Standardization |
CGIT | Frank | Rob | |||
Q4 | 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 | Conformance Tools |
Items might include:
|
CGIT | Rob | Frank | ||
Q2 | Conformance Strategy |
Discussion of Unified Strategy for Conformance
|
CGIT | Ioana | Frank | ||||
Lunch | |||||||||
PM | Q3 | Need to connect with InM to see if we will meet. | InM | ||||||
Q4 | Wrap-up and Admin |
|
CGIT | - | Frank | Nathan | |||
Day | Time | Icon | Ver. | Event | Host | joining | Chair | Scribe | |
Wednesday | AM | Q1 | not meeting | ||||||
Q2 | not meeting | ||||||||
Lunch | |||||||||
PM | Q3 | FHIR | FHIR discussions
|
CGIT | FHIR, Templates, Vocab | Frank | Frank | ||
Q4 | |||||||||
Day | Time | Icon | Ver. | Event | Host | joining | Attend | Scribe | |
Thursday | AM | Q1 | V2/V3/FHIR | Continuation of Discussions from Weekly Calls
|
Vocab | CGIT | Nathan, Frank, Rob | - | |
Q2 | Tooling Vocab |
|
Tooling Vocab |
CGIT | Rob, Frank | - | |||
Lunch | |||||||||
PM | Q3 | Tooling Vocab |
|
Tooling 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
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
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)
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??