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
 
(112 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=
==July 13, 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/20150617-Imn_minutes.docx June 17, 2015 Minutes]
+
#* [[InM_0309_R1_2a2c_Reconciliation|Reconciliation]]
*V2 Issues
 
**Hans:
 
<pre> As we were addressing a question on trigger events, message types, and message structures in the context of OO we ran into the following statement in Chapter 2, Section 2.5.1 that does not appear to be accurate.  It states:
 
“There is a one-to-many relationship between message types and trigger event codes. The same trigger event code may not be associated with more than one message type; however a message type may be associated with more than one trigger event code.”
 
While we agree that it is inappropriate for trigger event R01 to appear both under ORM and ADT, it is allowed with ACK.  So it seems that this statement should include “except when specified as part of an ACK message” or something like that.
 
 
How would you like to manage this?  I could submit a V2.9 proposal.  You could consider it a technical correction and manage it accordingly.  Other?</pre>
 
*Hans:<pre>•        Table HL70354 update – We realized that the following message structures were not yet added to the table:
 
#   Value          Events              Comments
 
#   ORL_O40  O40                  new message structure with optional Patient group
 
#  ORL_O41  O22                  new message structure with optional Patient group
 
#  ORL_O42  O34                  new message structure with optional Patient group
 
#  ORL_O43  O36                  new message structure with optional Patient group
 
#        It is possible that a trigger event uses multiple message structures (e.g., trigger event uses both ORL_O23 and ORL_041 depending on the intended content).  However, the text in either Chapter 2 or with table HL0354 is not totally clear on that.  We reached an understanding that this is valid in 2013, but it would be good that as part of the update below it also would be made very clear that it is permissible for a trigger event to deploy multiple message structures.  If this is already stated and we overlooked it, can you point us to that?
 
  
Thank you!
+
=archive=
</pre>
+
==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