This wiki has undergone a migration to Confluence found Here

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

From HL7Wiki
Jump to navigation Jump to search
 
(103 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.
*If we are doing DAF reconciliation:
+
***There are apps for Windows, Android, and Apple.
** GTM https://global.gotomeeting.com/join/306592429
+
***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.
** Use the phone line for audio
+
***International Dial-In Numbers: https://www.freeconferencecall.com/wall/ajulian/#international
  
=Agenda=
+
= Agenda - March  8, 2017=
== August 10, 2015==
+
# Management
*Roll call(5 minutes)
+
#* Approval of [http://www.hl7.org/documentcenter/public/wg/inm/minutes/20170117-InM-WGM-Minutes.docx minutes of the WGM]
*Approval of minutes (5 minutes)
+
#Metholodogy
**[http://www.hl7.org/documentcenter/public/wg/inm/minutes/20150727-Inm_Minutes.docx July 27, 2015 Minutes]
+
#* [[InM_0309_R1_2a2c_Reconciliation|Reconciliation]]
*DAF reconciliation
 
**[http://www.hl7.org/documentcenter/public/ballots/2015MAY/reconciliation/recon_fhir_daf_r1_d1_2015may.xls ballot spreadsheet]
 
*Table 0203 change request (Frieda)
 
** Add two new identifier types to Table 0203. HPID and OEID.
 
**Proposal 742_rev
 
***Please add these two identifier types to HL7 Table 0203 – Identifier Type and update existing note on ‘NH’. 
 
***XV - proposed addition for the CMS Health Plan Identifier, in lieu of HPID, because this is the identifier value selected by X12 for use in the HIPAA transactions.  See Info from Attachments Work Group Co-Chair re: X12, and the extract from X12 transaction for providers.  Germany has district values in Table 0203 for Health Plan (Payor) Identifier (NIIP) so there seems to be precedence for different values for different realms. 
 
***NH – suggest deleting the note re: using NH in the US; this was added to HL7 when Chapter 2C was created in V2.7, however CMS has not previously established and mandated a national identifier so ‘NH’ is not in use in the US.
 
***Suggest retain OEID in HL7 because X12  did not create a distinct value for this concept; X12 is using XV for both HPID and OEID as explained in notes from Craig Gabron, Attachments Work Group Co-chair..
 
*Vocab issues:
 
**Motion: To leave the typo of time as tiem in deprecated table 48 in versions prior to 2.5
 
**Motion: CNQ cancel query missing from table 0003 in Chapter 2, 2.a in 2.4- Publish errata
 
**Motion: ROR - in 2.3.1 R0R(RzeroR) was added - a typo - note erroneous. Publish errata to use ROR instead.
 
**Table 76
 
***  Motion: QCK description was Query General Acknowledgment description was changed to Deferred Query.
 
** Table 156
 
*** Motion: Fix spelling of 'filling' in REP - removed in2.7
 
**Motion: Policy statement on case sensitivity of normative code values: 
 
***All NORMATIVE HL7 defined code values SHALL be uppercase.
 
  
 +
=archive=
 +
==FHIR Evote Items - Close 20170209==
 +
[[Inm_fhir_evot_20170209 | InM Fhir Evote Results ]]
  
* Other business and planning (5 minutes)
+
==V2 Evote - Close 20170209==
*adjournment
+
==20170209 Evote Results==
 +
#[[Inm_29_r1_recon | expanded reconciliation]]
 +
#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==
 +
[[InM_29_R1_2a2c_Reconciliation| Evote 2a 2c ]] Passed 3-0-0
 +
 
 +
 
 +
#Management
 +
#*[[20170509_InM_Madrid_agenda | Madrid 2017  Agenda]]
 +
# Adjournment
 +
 
 +
==FHIR ToDos==
 +
#[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