This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

OrganizationAffiliation FHIR Resource Proposal

From HL7Wiki
Jump to navigation Jump to search


This resource has been added as a draft into the build as OrganizationRole (but highly likely to be renamed as requested here)

Patient Administration

Patient Administration

Committee Approval Date:

7 Feb 2018 (Brian Postlethwaite, Simone Heckmann 3-0-0)

Contributing or Reviewing Work Groups

  • None

FHIR Resource Development Project Insight ID


Scope of coverage

(need to differentiate from Organization)

A formally or informally recognized relationship between organizations for the purpose of achieving some form of collective action. Includes membership with a Health Information exchange, a separate physician organization, or any other relationships where the entities are separate business entities.

The Organization.partOf is used to form a hierarchical relationships within an organization which eventually resolves to a single organization. Each child in the tree is a subdivision of the parent. The OrganizationAffiliation is used to describe the relationship between two distinct organizations. It does not require a hierarchical relationship.

A resource instance is for a singular linkage between 2 organizations (it does not contain all members)

RIM scope


Resource appropriateness

This resource may be used to identify and describe relationships between two distinct organizations. This resource should not be used when the affiliates are part of a single organization.

Expected implementations

This resource is required to support Healthcare and Provider Directories. (Such as the Validated Healthcare Directory IG)

The Argonauts, Michigan Health Information Exchange Network, Sequoia Project, and other implementers have requested support for affiliate relationships.

Any solution that needs to store the relationships between its partner organizations will utilize this resource

Content sources

Not Applicable.

Example Scenarios

Preferred referral partners, trading partners, members of network or community.

Resource Relationships


It will also reference other resources that may be relevant to the association (such as HealthcareServices)


Include with R4 ballot.

gForge Users

Brian Postlethwaite Cooper Thompson Andrew Torres

When Resource Proposal Is Complete

When you have completed your proposal, please send an email to