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

Difference between revisions of "2015-c1-Inm current-info"

From HL7Wiki
Jump to navigation Jump to search
 
(82 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
=logistics=
 
=logistics=
* Conference call Mondays at 3:00pm U.S. Eastern
+
PLEASE USE web meeting below:
* Phone audio  1 770 657 9270
+
**Please join my meeting from your computer, tablet or smartphone. https://www.freeconferencecall.com/wall/ajulian
* code 984125#
+
***You can also dial in using your phone.
There is NO DAF reconciliation planned for February 8, so no GTM
+
***There are apps for Windows, Android, and Apple.
*If we are doing DAF reconciliation:
+
***If you join the meeting first, you will see the Dial-in number, Access code, and PIN that will associate your phone with your meeting session.
** GTM https://global.gotomeeting.com/join/306592429
+
***International Dial-In Numbers: https://www.freeconferencecall.com/wall/ajulian/#international
** Use the phone line for audio
 
  
=Agenda=
+
= Agenda - March  8, 2017=
== February 8, 2016 ==
+
# Management
*Management
+
#* Approval of  [http://www.hl7.org/documentcenter/public/wg/inm/minutes/20170117-InM-WGM-Minutes.docx minutes of the WGM]
**Roll call(5 minutes)
+
#Metholodogy
**[http://www.hl7.org/documentcenter/public/wg/inm/minutes/20160112-InM%20Minutes%20Orlando.docx Orlando WGM Minutes]
+
#* [[InM_0309_R1_2a2c_Reconciliation|Reconciliation]]
*Methodology
 
**[http://gforge.hl7.org/gf/project/inm_messaging/tracker/?action=TrackerItemEdit&tracker_item_id=9376&start=0  Issue with XAD]
 
*Management
 
**Table 203 changes.
 
**DAF notification of ballot.
 
* Other business and planning (5 minutes)
 
*adjournment
 
  
==Notes from 2/8/2016 meeting==
+
=archive=
 +
==FHIR Evote Items - Close 20170209==
 +
[[Inm_fhir_evot_20170209 | InM Fhir Evote Results ]]
  
* On call
+
==V2 Evote - Close 20170209==
** Tony (Chair)
+
==20170209 Evote Results==
** Dave Shaver
+
#[[Inm_29_r1_recon | expanded reconciliation]]
** Mead Walker
+
#InM Discovered issue:
** Mark Jones
+
#*In section 2.14.9 HL7 Attribute Table - MSH -Message Header shows the LEN of field 2 4..5.
** Freida Hall
+
#**But the text clearly states " This field contains five characters in the following order".
** Brett
+
#**This is broken in 2.8, 2.8.1, 2.8.2.
===Meeting minutes===
+
#**In 2.7  and 2.7.1 the table says len =  4..5, but the text says four characters.
* Motion by accept by Dave; Brent second; carried 4-0-1
+
#*'''Motion''' to correct 2.9.
 +
#*'''Motion''' to issue errata on 2.8, 2.8.1, 2.8.2 to change the table from 4..5 to 5 - since the text is normative.
 +
#*'''Motion''' to issue errata on 2.7, 2.7.1 to change the text to "five characters" and the LEN in the table to 5.
 +
==V2 Cp 2a and 2c Evote - Close 20170223==
 +
[[InM_29_R1_2a2c_Reconciliation| Evote 2a 2c ]] Passed 3-0-0
  
===XAD Issue===
 
* Mead presented the issue as outlined on gforge tracker
 
* Freida Hall added some points
 
* Mead's motion: "XAD.8 use as city limit indicator is consistent with usage within an implementation guide."; second by Brett
 
* Discussion re: choices; Dave concerned with usage is it feels 'odd'. No better slot suggested
 
* Dave requested that Mead submit 2.10 proposal to modify description of XAD.8 to describe this use of the component; Mead agreed.
 
* Carries 4-0-2
 
  
===Table 203===
+
#Management
* Freida provided description. Extending the P/D/T table to include "V" for validation, "N" for non-production
+
#*[[20170509_InM_Madrid_agenda | Madrid 2017  Agenda]]
* Additional clarification regarding "D", "P", and "T" usage
+
# Adjournment
* Fredia's description on the co-chair's list: "OO has approved a proposal to add new values to HL7 Table 0103, hopefully in V2.9. The original proposal was to add a single value “V-Validation”, however, in the course of discussion, OO also identified revisions to the definition of MSH-11 Processing ID and the associated PT (Processing Type) data type, and an additional table value and clarificationsDetails are in the attached Harmonization Proposal; this is using the new form from the Vocabulary Work Group distributed by Ted Klein.  The V2 database proposal #is 844 .  (OO Co-chairs, this is on the OO wiki as OO CR 187-844)"
+
 
* Mark moves to take this to Harmonization; Freida seconds
+
==FHIR ToDos==
* Carries 6-0-0
+
#[http://lists.hl7.org/read/archive?id=307213 FHIR to-dos] All done!
 +
 
 +
==V2 Todos==
 +
#V2.8.2 table 357 metadata says err-4 , should be err-3
 +
#Update CP2 ERR to further explain use of ERR segment.
 +
#Update CP2  
 +
==Future==
 +
# [[V2Tables452-454 | V2 Tables 454, 453, 454] - Fixed in harmonization]
 +
#Tackle Backward compatibility in V2
 +
#Publish policy on pre-adoption in V2 through V2 Publishing

Latest revision as of 20:23, 11 April 2017

logistics

PLEASE USE web meeting below:

Agenda - March 8, 2017

  1. Management
  2. Metholodogy

archive

FHIR Evote Items - Close 20170209

InM Fhir Evote Results

V2 Evote - Close 20170209

20170209 Evote Results

  1. expanded reconciliation
  2. InM Discovered issue:
    • In section 2.14.9 HL7 Attribute Table - MSH -Message Header shows the LEN of field 2 4..5.
      • But the text clearly states " This field contains five characters in the following order".
      • This is broken in 2.8, 2.8.1, 2.8.2.
      • In 2.7 and 2.7.1 the table says len = 4..5, but the text says four characters.
    • Motion to correct 2.9.
    • Motion to issue errata on 2.8, 2.8.1, 2.8.2 to change the table from 4..5 to 5 - since the text is normative.
    • Motion to issue errata on 2.7, 2.7.1 to change the text to "five characters" and the LEN in the table to 5.

V2 Cp 2a and 2c Evote - Close 20170223

Evote 2a 2c Passed 3-0-0


  1. Management
  2. Adjournment

FHIR ToDos

  1. FHIR to-dos All done!

V2 Todos

  1. V2.8.2 table 357 metadata says err-4 , should be err-3
  2. Update CP2 ERR to further explain use of ERR segment.
  3. Update CP2

Future

  1. [[V2Tables452-454 | V2 Tables 454, 453, 454] - Fixed in harmonization]
  2. Tackle Backward compatibility in V2
  3. Publish policy on pre-adoption in V2 through V2 Publishing