Patient Administration Call
|PA Work Group Conference Call
Local numbers sent to list
|PA Work Group Conference Call
|Date: Tuesday, June 20, 2017
Time: 12:00 PM (US Pacific Time, GMT -7)
Quorum Met (Chair+2, Yes/No)? Yes
||Nasjonal IKT, Norway
||Alex de Leon
||Kaiser Permanente, USA
- Directory Resources in Australia
Argonaut Scheduling Project update
Progressing well, 2 operations in definition
1. Appointment/slot finding (to be able to select for booking)
2. Appointment Booking
Appointment booking is to mask more of the complexity of other activities that need to occur behind the scenes, such as patient pre-registrations and locating other resources etc to complete all the details
Organization Affiliation Introduction/Review
The org affiliation resource represents a relationship between 2 organiations that is not a part of. E.g. for Business partners etc.
An OrganizationAffiliation denotes a formal relationship between an Organization and another Organization in which the member participates or has participated. These fields are implemented using the FHIR Extensibility mechanism as instances of the FHIR Basic resource.
id – [0..1] Inherited from Resource. The ID of the OrganizationAffiliation
identifier – [0..1] An Identifier by which the member is known to the owner
type – [1..1] A CodeableConcept that denotes the type of the membership. See Organization Affiliation Types, below.
owner – [1..1] A Reference to an Organization that has the members
member – [1..1] A Reference to an Organization
endpoint – [0..*] References to Endpoints (expect this to become an extension)
period – [0..1] A Period that defines the effective dates of this membership
Contrast: Linkage covers joining to resources that represent the same concept, should we be creating a more general relationship to associate things.
This was discussed in Madrid at the WGM, and the concern on the abuse of the concept to extend relationships where not really desired, and not ease interoperability.
This proposed generic resource would represent the many to many resource references (not one to many relationships).
There are other resources such as the HealthcareService which is closer to a “triple” relationship rather than just a 2 part relationship.
Propose to take this to the FHIR Infrastructure team to consider if this would even get support there.
Question on the usage of the endpoint here, which end is it associated with?
How do we represent peer relationships that have no apparent owner. (not sure on the scale of this issue)
e.g. ACO (Accountable Care Organization)
Verification of validity of the relationship (2 way confirmation) may be needed when using externally (not a problem internally)
Alternative to the owner/member could be using a single multi-card property for members, but then makes it less clear about when to use more than 2 member properties, and when to use more records.
Owner/member could also be source/target
The relationship as discussed usually has a direction.
Further review the Org Affilliation
Provider Directory Project Update (Brian)
|Next Meeting/Preliminary Agenda Items|
- Next telecom meeting: Tuesday 17.06.27
Return to PA Main Page
© 2017 Health Level Seven® International. All rights reserved.