CapabilityStatement-plan-net

Sourcehl7.fhir.us.davinci-pdex-plan-net#current:DaVinci PDEX Plan Net (v4.0.1)
resourceTypeCapabilityStatement
idplan-net
canonicalhttp://hl7.org/fhir/us/davinci-pdex-plan-net/CapabilityStatement/plan-net
version1.1.0
statusactive
publisherHL7 Financial Management Working Group
nameDavinciPdexPlanNetCapabilityStatement
titlePlan-Net CapabilityStatement
date2022-03-18
experimentalfalse
descriptionThis 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.
jurisdictionsus
kindrequirements
fhirVersion4.0.1
formatsxml json application/json-patch+json
implementationGuideshttp://hl7.org/fhir/us/davinci-pdex-plan-net/ImplementationGuide/hl7.fhir.us.davinci-pdex-plan-net
Usages(none)

DavinciPdexPlanNetCapabilityStatement

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.

Mode SERVER
Description

The Plan-Net Server SHALL :

  1. Support all profiles defined in this Implementation Guide..
  2. Implement the RESTful behavior according to the FHIR specification.
  3. 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.
  4. Support json source formats for all Plan-Net interactions.
  5. Identify the Plan-Net profiles supported as part of the FHIR meta.profile attribute for each instance.
  6. 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.
Transaction
System History
System Search
Resource Type Profile Read V-Read Search Update Create
Endpoint Supported profiles:
   Plan-Net Endpoint 		y y y
HealthcareService Supported profiles:
   Plan-Net HealthcareService 		y y y
InsurancePlan Supported profiles:
   Plan-Net InsurancePlan 		y y y
Location Supported profiles:
   Plan-Net Location 		y y y
Organization Supported profiles:
   Plan-Net Network
   Plan-Net Organization 		y y y
OrganizationAffiliation Supported profiles:
   Plan-Net OrganizationAffiliation 		y y y
Practitioner Supported profiles:
   Plan-Net Practitioner 		y y y
PractitionerRole Supported profiles:
   Plan-Net PractitionerRole 		y y y

Produced 08 Sep 2023