# description
This Section describes the expected capabilities of the Plan-Net Server actor which is responsible for providing responses to the queries submitted by the Plan-Net Requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by Plan-Net Servers are defined. Systems implementing this capability statement should meet the CMS FInal Rule requirement for provider directory access.  Plan-Net  Clients can use the required capabilities to access necessary data based on their local use cases and other contextual requirements.

# rest[].documentation
The Plan-Net  Server **SHALL**:

1. Support all profiles defined in this Implementation Guide..
1.  Implement the RESTful behavior according to the FHIR specification.
1. Return the following response classes:
   - (Status 400): invalid parameter
   - (Status 401/4xx): unauthorized request
   - (Status 403): insufficient scope
   - (Status 404): unknown resource
   - (Status 410): deleted resource.
1. Support json source formats for all Plan-Net interactions.
1. Identify the Plan-Net  profiles supported as part of the FHIR `meta.profile` attribute for each instance.
1. Support the searchParameters on each profile  individually and in combination.
1.Support forward and reverse chaining on all search parameters that specify the 'chain' property

The Plan-Net  Server **SHOULD**:

1. Support xml source formats for all Plan-Net  interactions.

# rest[].security.description
1. See the [General Security Considerations](implementation.html#general-security-considerations) section for requirements and recommendations.
1. A server **SHALL** reject any unauthorized requests by returning an `HTTP 401` unauthorized response code.