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
Line 8: Line 8:
  
 
=Agenda=
 
=Agenda=
==July 13, 2015==
+
==July 20, 2015==
 
*Roll call(5 minutes)
 
*Roll call(5 minutes)
 
*Approval of minutes (5 minutes)
 
*Approval of minutes (5 minutes)
 
**[http://www.hl7.org/documentcenter/public/wg/inm/minutes/20150617-Imn_minutes.docx June 17, 2015 Minutes]
 
**[http://www.hl7.org/documentcenter/public/wg/inm/minutes/20150617-Imn_minutes.docx June 17, 2015 Minutes]
 +
*DAF reconciliation
 +
**[http://www.hl7.org/documentcenter/public/ballots/2015MAY/reconciliation/recon_fhir_daf_r1_d1_2015may.xls ballot spreadsheet]
 
*V2 Issues
 
*V2 Issues
 
**Hans:
 
**Hans:

Revision as of 18:46, 20 July 2015

logistics

Agenda

July 20, 2015

 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?
  • Hans:
    •         Table HL70354 update – We realized that the following message structures were not yet added to the table:
  1. Value Events Comments
  2. ORL_O40 O40 new message structure with optional Patient group
  3. ORL_O41 O22 new message structure with optional Patient group
  4. ORL_O42 O34 new message structure with optional Patient group
  5. ORL_O43 O36 new message structure with optional Patient group
  6. 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!

  • Other business and planning (5 minutes)
  • adjournment