Gotomeeting - https://global.gotomeeting.com/join/311685429
HL7 Conference Call phone number
US/Canada: Phone: +1 770-657-9270, Participant Code: 986210
for non-US participants: https://www.intercallonline.com/listNumbersByCode.action?confCode=4603612751
Chair: Irma Jongeneel
Scribe: Alex de Leon
The WG discussed the following based on request from Peter Bomberg:
There is no mechanism to associate contacts to a location, we need to associate several different contacts to a location, where each contact has a role and a start/end date for their association
The main request would be for tying contact to a particular role with a timeframe. The group discussed for sign off that this might be served by PractitioinerRole which can be linked to location.
This can be used.
The proposal was to remove the location telecom
Replicate the organization.contact backbone element in location.
This discussion will probably spawn a new Jira item for removing Orgainization.telecom element and recommend using the contact backbone element with reason to communicate what that telecom info is used for.
Cooper moves to disposition this as persuasive with modifications. Brian seconds.
Vote (for/against/abstain): 6/0/1
The following was used for reference:
- Cooper Thompson Potential Role-specific elements within the contact data type - - FHIR-29035Getting issue details... STATUS
- Cooper Thompson Remove telecom address from Organization - - FHIR-29034Getting issue details... STATUS
- Cooper Thompson Create set of extensions for period on the contact backbone - FHIR-
The Location resource has a status element, but lacks the status change date or status effective aspects, which is required to track when a status change occured.
The WG moved on to discuss the virtual WGM
Brian expressed that this was of value.
The 3 sessions that we had seem to be optimal. Adding more probably would not add value.
It was difficult to gain participation of non participatory members
Non verbal communication was difficult to see.