Organization Affiliation
Introduction
Constraint
Anticipated Queries
Examples
More Information
Practitioner
PractitionerRole
URLs
© 2021-2022 Opala. All Rights Reserved.
Version 1.1.0.0
The OrganizationAffiliation resource profile describes relationships between two or more organizations. These services include: the services one organization provides to another, the location(s) where they provide services, the availability of those services, electronic endpoints, etc.
The OrganizationAffiliation structure is derived from the FHIR R4 HealthcareService resource. The OrganizationAffiliation resource defines an affiliation/association/relationship between two distinct organizations.
This structure refers to the following:
ID | Path | Details |
---|---|---|
organization-or-participatingOrganization | OrganizationAffiliation | PlannetOrganizationAffiliation.organization or PlannetOrganizationAffiliation.participatingOrganization : organization.exists() or participatingOrganization.exists() |
Use Postman to test Opala's Provider Directory API by querying the API and returning the results. The Opala Collection is a group of API requests that are already saved in the Postman app and arranged in folders. Within each folder are pre-defined requests that you can run as-is or modify to fit your own needs.
See the Setting Up Postman topic in this documentation set for information on how to import the Opala Collection into your local copy of Postman.
You can view Opala's Capability Statement at https://api.opalahealth.io:45000/pdir/premera/v1/fhir/r4/metadata
for a description of the Provider Directory API to assist you in making your queries.
Retrieve all OrganizationAffiliation resources.
GET {{base_url}}/OrganizationAffiliation
Select OrganizationAffliliations that are part of the specified type.
GET {{base_url}}/OrganizationAffiliation
?role
=[role]
Select OrganizationAffliliations with a specific identifier.
GET {{base_url}}/OrganizationAffiliation
?identifier
=[identifier]