Difference between revisions of "OrganizationAffiliation FHIR Resource Proposal"
Bamarquard (talk | contribs) |
Bamarquard (talk | contribs) |
||
| Line 81: | Line 81: | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | |||
| + | Preferred referral partners, trading partners, members of network or community. | ||
==Resource Relationships== | ==Resource Relationships== | ||
Revision as of 20:26, 17 February 2017
This page documents a Pending FHIR Resource Proposal
Contents
- 1 OrganizationAffiliation
- 1.1 Patient Administration
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
OrganizationAffiliation
Patient Administration
Committee Approval Date:
Please enter the date that the committee approved this Resource proposal
Contributing or Reviewing Work Groups
- None
FHIR Resource Development Project Insight ID
FHIR STU3
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.
RIM scope
Unknown.
Resource appropriateness
This resource may be used to identify and describe relationships between two distinct organization. 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.
The Argonauts, Michigan Health Information Exchange Network, Sequoia Project, and other implementers have requested support for affiliate relationships.
Content sources
Not Applicable.
Example Scenarios
Preferred referral partners, trading partners, members of network or community.
Resource Relationships
Timelines
gForge Users
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
