Plan-Net Organization (7.58.1)

The Organization resource profile describes a formal or informal grouping of people or organizations with a common purpose (e.g., company, institution, corporation, community group, healthcare practice).

Note: When the contact is a department rather than a human (e.g., patient help line), add the department name in contact.name.text and include blank family and given name fields.

The Organization profile is based on the U.S. Core Organization profile. Both the Plan-Net Network and Organization profiles are based on this Organization profile. To selectively query only Network profiles, search for type = ntwk. To selectively query only Organization profiles, search for type = fac,bus,prvgrp,payer,atyprv.

This structure refers to the following:

• Structure
  • plannet-Organization
• Extensions
  • qualification
  • org-description
  • location-reference
  • contactpoint-availabletime
  • via-intermediary
  • geolocation

Search Details

Since the Plan-Net Network and Organization profiles are both based on the Organization profile, you must distinguish which of these you want to search for if you want to narrow your search. To selectively query only Network profiles, search for type = ntwk. To selectively query only Organization profiles, search for type = fac,bus,prvgrp,payer,atyprv.

Note: Unlike Plan-Net, CARIN for Blue Button^® does not have a separate Network resource profile; all Network parameters are handled by the Organization resource in C4BB.

References

Many of the defined elements in a resource are references to other resources. Using these references, the resources combine to build a web of information about healthcare. The Network profile references these resources:

• Plan-Net Location
• Plan-Net OrganizationAffiliation
• Plan-Net Organization
• Plan-Net PractitionerRole

Anticipated Queries

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.

Search Organization

Retrieve all Organization resources. An organization can be a company, institution, corporation, community group, or healthcare practice.

Guidance: When the contact is a department name, rather than a human (e.g., patient help line), include a blank family and given name, and provide the department name in contact.name.text

GET {{base_url}}/Organization

Search by Name

Select an Organization with a specific name.

GET {{base_url}}/Organization?name=[name]

Search by Type

Select Organizations that are part of the specified organization.

GET {{base_url}}/Organization?partof=[partof]

GET {{base_url}}/Organization?type=[type]

Search by Address

Select Organizations that are at a specified location.

GET {{base_url}}/Organization?address-use=[address-use]

GET {{base_url}}/Organization?organization-address=[organization-address]

Examples

• Acme (Payer)
• Connecticut HIE (Atypical Provider)
• Hamilton Clinic (Facility)
• Pharmacy Chain (Provider Group)

More Information about the plannetOrganization profile

• Plan-Net Organization Snapshot Table (Must Support) (7.58.1.2)
• Plan-Net Organization Terminology Bindings (7.58.1.2.1)
• Plan-Net Organization Detailed Descriptions (7.58.5)
• ValueSet: Organization Type VS (7.91.1)
• CodeSystem: Organization Type (7.107.1)
• FHIR Resource References (2.3.0)