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
Line 10: Line 10:
 
***International Dial-In Numbers: https://www.freeconferencecall.com/wall/ajulian/#international
 
***International Dial-In Numbers: https://www.freeconferencecall.com/wall/ajulian/#international
  
= Agenda - February 8, 2017=
+
= Agenda - March  8, 2017=
 
# Management
 
# Management
 
#* Approval of  [http://www.hl7.org/documentcenter/public/wg/inm/minutes/20170117-InM-WGM-Minutes.docx minutes of the WGM]
 
#* Approval of  [http://www.hl7.org/documentcenter/public/wg/inm/minutes/20170117-InM-WGM-Minutes.docx minutes of the WGM]

Revision as of 16:25, 13 February 2017

logistics

Agenda - March 8, 2017

  1. Management
  2. Metholodogy
    • V2 referred to telcon : Line item 7,23,24,32,88,89 have been removed from the block vote

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


  1. Management
  2. Adjournment

FHIR ToDos

  1. FHIR to-dos

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. V2 Tables 454, 453, 454
  2. Tackle Backward compatibility in V2
  3. Publish policy on pre-adoption in V2 through V2 Publishing