Date:  

Facilitator:  @

Note Taker: @ 

Attendees

Present
Name
Affiliation
(tick)Mayo Clinic
(tick)United Healthcare
(tick)Kaiser Permanente
(tick)Vernetzt, LLC
(tick) Altarum     
(tick)
(tick)Robert Dieterle
(tick)Finnie Flores
(tick)Lantana Consulting Group


















Create Decision from template

Agenda Topics

Agenda Outline
Agenda Item
Meeting Minutes from Discussion
Decision Link(if not child)
Management Minute Approval

MethodologyAlerts PSS11-0-0
Methodology


Tracker 18082

Tracker 24635

18082 Ulrike Merrick / Sandra Stuart Change to no action required. 

6-0-0

Tracker23723

Nick Radov / Ulrike Merrick

persuasive with mod:  Change cardinality and update text in tracker.


8-0-0

Tracker 20704

Tabled    see disposition in tracker.

Also, Messaging description page http://build.fhir.org/messaging.html as well as http://build.fhir.org/messageheader.html needs to more clearly describe ID and identifier.

Notes:

Add messageHeader.identifier – this would be a business identifier, so cardinality should be 0..*, type = identifier – add in before event – there as comments from Lloyd and Hans – should ask both of them to be in the room for discussion.

Would there be a reason to reference just the messageHeader by itself? = to know who made the message and sent it to whom potentially

It seems you can only have 1 message per bundle, since bundle = message

messageDefinition is using the URI as the business identifier and = Rick will log a tracker for this

when the recipient parsed the bundle, then the bundle identifier is gone how would the recipient know who created the bundle

Where to map MSH-10 to? Looks like bundle.identifier

Change the definition of MessageHeader.response.identfier:

The bundle.identifier of the received bundle where bundle.type = message and change type from ID to Identifier – cardinality 1..1

From v2 mapping perspective MSH has been split across 2 resources into bundle and messageHeader

Find not persuasive with mod.

Also need to update the text on messaging to give more guidance – also add some guidance to the message header as well explaining how to handle the message identifier

Section 3.4.1.4 – needs to get cleaned up to highlight the difference between IDs and identifiers = Rick to add a new tracker = #24645

7-0-0

Tracker 20522

REF: 21644. Persuasive with Mod. Ulrike Merrick / Rick Geimer 

MessageHeader.source.endpoint:

If source is Required but all children are optional, then you MUST pick at least one of the children = see#21644

Asking for in person from V2FHIR project – but we think of making these elments optional should be ok.

Motion to find persuasive with mod: will make MessageHeader.source.endpoint and MessageHeader.target.endoint optional = Nick Radov, Rick Geimer, no further discussion, against:0, abstain: 0, in favor: 7

7-0-0
Management Next agenda

 Adjournment
 Adjourned at

Supporting Documents

Outline Reference
Supporting Document
Minute Approval
TrackersTracker23723

Tracker 20704

Tracker 20522

Tracker 18082
Alerts PSSPSS for Notifications (formerly known as Alerts)



Action items

  •