This wiki has undergone a migration to Confluence found Here
Difference between revisions of "OrganizationAffiliation FHIR Resource Proposal"
Jump to navigation
Jump to search
Bamarquard (talk | contribs) (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| (23 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =OrganizationAffiliation= |
| + | This resource has been added as a draft into the build as OrganizationRole (but highly likely to be renamed as requested here) | ||
| − | + | ==Patient Administration== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [ | + | [http://wiki.hl7.org/index.php?title=Patient_Administration Patient Administration] |
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | + | 7 Feb 2018 (Brian Postlethwaite, Simone Heckmann 3-0-0) | |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| − | + | * None | |
| − | * | ||
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| + | 1345 | ||
| − | + | ==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== | ==RIM scope== | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| + | |||
| + | Unknown. | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 76: | Line 60: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | 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== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent 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== | ==Content sources== | ||
| Line 86: | Line 79: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | |||
| + | Not Applicable. | ||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- 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== | ||
| Line 101: | Line 98: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | Organization | ||
| + | |||
| + | It will also reference other resources that may be relevant to the association (such as HealthcareServices) | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | Include with R4 ballot. | ||
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| + | |||
| + | Brian Postlethwaite | ||
| + | Cooper Thompson | ||
| + | Andrew Torres | ||
==When Resource Proposal Is Complete== | ==When Resource Proposal Is Complete== | ||
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]''' | '''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]''' | ||
Latest revision as of 19:41, 7 March 2018
This page documents a Approved 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
This resource has been added as a draft into the build as OrganizationRole (but highly likely to be renamed as requested here)
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
1345
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
Unknown.
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
Organization
It will also reference other resources that may be relevant to the association (such as HealthcareServices)
Timelines
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 FMGcontact@HL7.org
