This wiki has undergone a migration to Confluence found Here

2015-c1-Inm current-info

From HL7Wiki
Jump to navigation Jump to search

logistics

Agenda - January 30, 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

  1. V2 ballot Reconciliation Reconciliation spreadsheet
  2. See expanded reconciliation
    • 7 Motion to find Answered Group InM-1 Items 6, 91
    • 8 Motion to find Persuasive Group InM-2 Items 1,62,65,85,86,87,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147
    • 9 Motion to find persuasive with mod Group InM-3 Items 7,8,9,10,23,24,32,63,88,89,90,112,131,132
      • Grouping InM-3 Items 7,8,9,10,23,24,32,63,88,89,90,112,131,132
      • 7,23,24,32,88,89 removed from block for further refinement/discussion
      • 9, 10 persuasive - editor will use provided text
      • 8,32,63,112,131,132 - persuasive with mod - Editor will fix as indicated
    • 10 Motion to find Out of scope Group InM-4 Items 59,61,102,103,104
    • 11 Motion to find Out of Scope Group InM-5 Item 98
  3. 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.


  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