Difference between revisions of "OrganizationAffiliation FHIR Resource Proposal"
Bamarquard (talk | contribs) |
Bamarquard (talk | contribs) |
||
| Line 24: | Line 24: | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| − | * | + | * None |
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | FHIR STU3 | |
==Scope of coverage== | ==Scope of coverage== | ||
(need to differentiate from Organization) | (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. | 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. | ||
| − | |||
| − | |||
| Line 56: | Line 55: | ||
* 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 inter-organization relationships when two different organizations have separate parent organizations. This resource should not be used when the affiliates are owned by 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. | ||
| + | |||
| + | The Argonauts, Michigan Health Information Exchange Network, Sequoia Project, and other implementers have requested support for affiliate relationships. | ||
| + | |||
==Content sources== | ==Content sources== | ||
Revision as of 15:57, 7 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.
RIM scope
Resource appropriateness
This resource may be used to identify inter-organization relationships when two different organizations have separate parent organizations. This resource should not be used when the affiliates are owned by 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
Example Scenarios
Resource Relationships
Timelines
gForge Users
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
