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 27: Line 27:
 
==V2 Todos==
 
==V2 Todos==
 
#V2.8.2 table 357 metadata says err-4 , should be err-3
 
#V2.8.2 table 357 metadata says err-4 , should be err-3
#Update 2 ERR to further explain use of ERR segment.
+
#Update CP2 ERR to further explain use of ERR segment.
 +
#Update CP2 
 +
==Future==
 +
#Tackle Backward compatibility in V2
 +
#Publish policy on pre-adoption in V2

Revision as of 19:12, 18 January 2017

logistics

  • Conference call Second Monday of each month at 1:00pm U.S. Eastern
  • Phone audio 1 770 657 9270
  • code 984125#

Agenda - January 9, 2017

  1. Management
    • Approval of minutes of the WGM
  2. Metholodogy
    • MessageHeader edits:
      • Change example to use a prefered value.9920
      • Change MessageHeader.event.respons to 0..* 10121
      • Rename MessageHeader.data to MessageHeader.focus 6081
      • Ballot to approve [7037
      • Review Proposal 9125 9125
      • Review Proposal 12309 Add extension to enable response type including value set from Hl700??
      • Review proposal 12459

Change definition of MessageHeader.id to "" The MessageHeader.id of the message that this message is a response to"

      • WARNING:MessageHeader Resource elements are out of order.
        • The correct order is '[event(=what), destination(=who.focus), receiver(=who.focus), timestamp(=when.init), enterer(=who.author), author(=who.author), source(=who.actor), responsible(=who.witness), reason(=why)]'
        • but the actual order is '[timestamp(=when.init), event(=what), source(=who.actor), destination(=who.focus), enterer(=who.author), author(=who.author), receiver(=who.focus), responsible(=who.witness), reason(=why)]'
  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. Tackle Backward compatibility in V2
  2. Publish policy on pre-adoption in V2