Stream: implementers
Topic: Organization Relationships
Ken Sinn (Nov 24 2016 at 15:00):
Hi folks,
Have there been any discussions about expanding/increase the cardinality of "organization.partOf 0..1"?
We have use cases where hospitals have more than one type of roll-up, e.g. to a regional authority as well as a traditional organizational hierarchy.
Alternately, a relatedOrganization (0..*) that specifies both organization(reference) and relationship(codeableConcept) may be more robust.
Are there any other implementers that have implemented a similar use case?
Thanks for any thoughts you can provide!
Dunmail (Nov 24 2016 at 16:17):
I've encountered the same problem today, trying to use Organization to model ad-hoc groups of Organizations for access control when information sharing. A given organization will almost certainly be a member of more than group.
Dunmail (Nov 24 2016 at 16:18):
I looked at Group, but this is constrained so that it can't represent a Group of Organizations
Igor Sirkovich (Nov 24 2016 at 19:09):
I agree that relatedOrganization (0..*) would be a good fit as it would also cover relationships other that "part of", e.g. affiliation between hospitals, clinics, etc. If not in the core, maybe we can have a standard extension for this?
Brian Postlethwaite (Nov 27 2016 at 09:13):
There has been some discussions around this, but its more around assoications rather than part-of, and fits into your use-case. This is likely to be a seperate thing.
Sandeep Giri (Feb 17 2017 at 23:40):
We are facing the exact same problem -- in our case, we need to represent a hospital (or a clinic) may belong to multiple ACO (Accountable Care Organization) networks. So if a hospital Organization H1 belongs to 2 separate Organization resources ACO1 and ACO2, then we should be able to have references to both ACO1 and ACO2 within the H1 resource.
I also second the approach suggested by @Ken Sinn to have a relatedOrganization (0..*) attribute.
@Brian Postlethwaite -- since this seems to have come up multiple times with valid use cases, should we open this as an enhancement request in gForge?
Brian Postlethwaite (Feb 17 2017 at 23:55):
The draft resource proposal is here:
http://wiki.hl7.org/index.php?title=OrganizationAffiliation_FHIR_Resource_Proposal
Looking for comments on seperate resource vs property of org.
Considering how often these are likely to happen, how much history you are going to want to retain here into the future, and effect on the size of the resource as it gets older.
(seperate resource doesn't have these specific issues)
Last updated: Apr 12 2022 at 19:14 UTC
