Organization is a term used by FHIR to denote an informal or formal grouping of people. usually this concept is referred to as “groups” but since the term “groups” is ambiguous in a medical context, we are switching to the term “Organization”
In Care, organizations would be used to groups permissions assigned to resources. ie An organization might be created for all Doctors, this might include permissions to Questionnaires that are created and visible throughout the hospital, another organization called “Cardiology” could be created with access to cardiology specific forms.
This could go on with multiple use cases like, nurses in an organization “X” with access to patients in location Y,Z and so on..
Organizations help in grouping permissions in an ordered manner so that the next time a doctor comes along we don’t have to define individual permissions for them.
Organizations can be nested, ie Doctors will be an organization created at the root and “Cardiology” might be an organization created as its child. This would mean that all permissions associated with Doctors are implicitly available in the sub organization as well.
Although the current spec only involves organizations for permission management, they could very well be extended for building out more features.
Add support for care defined type of organisations. [https://build.fhir.org/valueset-organization-type.html]
In the case of palliative care the value set for these would be Volunteer, Asha Worker, MLSP, … The instance should have an option to create these orgs and set permissions for each. When creating a user we should have an option to select these types.