Provider Connect Australia (PCA)
24.2.0.0 - active

Provider Connect Australia (PCA) - Local Development build (v24.2.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## : PCA Subscriber Agent Capability Statement - XML Representation

Active as of 2024-09-23

Raw xml | Download

    <CapabilityStatement xmlns="http://hl7.org/fhir">
      <id value="pca-subscriber-agent"/>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CapabilityStatement pca-subscriber-agent</b></p><a name="pca-subscriber-agent"> </a><a name="hcpca-subscriber-agent"> </a><a name="pca-subscriber-agent-en-AU"> </a><h2 id="title">PCA Subscriber Agent Capability Statement</h2><ul><li>Implementation Guide Version: 24.2.0.0 </li><li>FHIR Version: 4.0.1 </li><li>Supported Formats: <code>application/fhir+json</code>, <code>application/fhir+xml</code></li><li>Supported Patch Formats: </li><li>Published on: 2024-09-23 10:57:22+1000 </li><li>Published by: Australian Digital Health Agency </li></ul><blockquote class="impl-note"><p><strong>Note to Implementers: FHIR Capabilities</strong></p><p>Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.</p></blockquote><h2 id="rest">FHIR RESTful Capabilities</h2><div class="panel panel-default"><div class="panel-heading"><h3 id="mode1" class="panel-title">Mode: <code>server</code></h3></div><div class="panel-body"><div><p>A PCA Subscriber Agent manages the service offerings for one subscriber organisation (also referred to as a 'business partner' in the PCA portal).</p>
    <p>The PCA service instantiates one PCA Subscriber Agent for each participating subscriber organisation. That is, each subscriber organisation interacts with a PCA Subscriber Agent located at a <em>subscriber agent base url</em> that is unique to that organisation.</p>
    <p>The <em>subscriber agent base URL</em> for a particular organisation is available via the PCA portal on the 'Organisation Details' screen of the subscriber organisation.</p>
    <p>A service offering is made available to a subscriber organisation when a publisher authorises publication of a resource to one or more of the subscriber organisation's partner services.</p>
    <p><strong>Publication process</strong></p>
    <p>A PCA Publisher Agent creates the <code>Location</code>, <code>HealthcareService</code> and <code>PractitionerRole</code> resources (that are associated with existing <code>Organization</code> and <code>Practitioner</code> resources) that represent their service offerings.  These resources are made available to a subscriber organisation when a publisher authorises publication of a <code>HealthcareService</code> or <code>PractitionerRole</code> resource to one or more of the subscriber organisation's partner services.</p>
    <p>The authority to publish is represented using <code>Contract</code> resources which are also implemented by the PCA Publisher Agent (see the <a href="CapabilityStatement-pca-publisher-agent.html#contract">Contract resource endpoint</a>).</p>
    <p><strong>Identifier disclosure rules</strong></p>
    <p>The PCA service enforces certain business rules regarding the disclosure of <em>Identifiers</em> (including subscriber-issued identifiers) in the resources that it makes available to subscribers.</p>
    <p>The result of these rules may be that a copy of  a resource received by one subscriber may contain <em>Identifiers</em> that are not included in the copy of the same resource that is received by a different subscriber.</p>
    <p>In the case of HPI-Is these <em>identifier disclosure rules</em> ensure that relevant legal requirements are complied with.</p>
    <p>Other <em>identifier disclosure rules</em> are defined by the PCA operator.</p>
    <p>The <em>identifier disclosure rules</em> are applied automatically at the time that the resource is retrieved by the target PCA Subscriber Agent.</p>
    <p><strong>Authorisation rules</strong></p>
    <p>Authorised client systems are only permitted to interact with a PCA Subscriber Agent API where the participating organisation associated with the PCA Subscriber Agent has a subscriber approval status of 'Approved'.</p>
    <p><strong>Resource profiles and extensions</strong></p>
    <p>This API specification defines the required resource profiles for each operation.  The PCA Subscriber Agent will reject any request to create or update a resource that contains any extensions (including modifier extensions) not explicitly defined in that resource profile.</p>
    </div><div class="lead"><em>Security</em></div><div class="row"><div class="col-lg-6">Enable CORS: yes</div><div class="col-lg-6">Security services supported: <code>OAuth</code></div></div><blockquote><div><p>This server implements OAuth2</p>
    </div></blockquote><div class="lead"><em>Summary of System-wide Interactions</em></div><ul><li>Supports the <code>search-system</code>interaction described as follows:<div><p><strong>Definition</strong>:<br/>
    This operation is a RESTful <em>search</em> interaction (whole system interaction), across multiple resource types (as described in the <a href="https://www.hl7.org/fhir/http.html#search">FHIR specification</a>).</p>
    <p><strong>Behaviour</strong>:<br/>
    This operation is used by a client system operated by a subscriber organisation to get resources that match the specified search parameters and that have been published to the subscriber organisation's partner services.</p>
    <p>The following  search parameters are supported:</p>
    <ul>
    <li>
    <p><em>_lastUpdated</em> is used to get the resources that have been added or changed since the requesting system last synchronised their local data store with PCA Subscriber Agent.  This search parameter supports the <code>gt</code> and <code>lt</code> comparison prefixes.</p>
    </li>
    <li>
    <p><em>_type</em> is used to filter the resources returned by their resource type. The available types are:</p>
    <ul>
    <li>
    <p><code>HealthcareService</code> (returns resources conforming to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile)</p>
    </li>
    <li>
    <p><code>PractitionerRole</code> (returns resources conforming to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile)</p>
    </li>
    <li>
    <p><code>Organization</code> (returns resources conforming to the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile)</p>
    </li>
    <li>
    <p><code>Location</code> (returns resources conforming to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile)</p>
    </li>
    <li>
    <p><code>Practitioner</code> (returns resources conforming to the <a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a> profile)</p>
    </li>
    <li>
    <p><code>Provenance</code> (returns resources conforming to the <a href="StructureDefinition-pca-provenance.html">PCA Provenance</a> profile)</p>
    </li>
    <li>
    <p><code>Contract</code> (returns resources conforming to the <a href="StructureDefinition-pca-publication-authorisation-record.html">PCA Publication Authorisation Record</a> profile)</p>
    </li>
    <li>
    <p><code>Task</code> (returns resources conforming to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile)</p>
    <ul>
    <li>Note: a <code>Contract</code> resource with 'status' of 'revoked' indiates that a service offering that was previously published to a partner service is no longer available to that partner service. In this case the <code>Contract</code> resource will reference a <em>target</em> <code>Organization</code>, <code>Location</code>, <code>HealthcareService</code>, or <code>PractitionerRole</code> that is not included in the <code>Bundle</code> (but its <em>id</em> will identify the resource which is no longer published to the subscriber).</li>
    </ul>
    </li>
    </ul>
    </li>
    <li>
    <p><em>_include</em> (and <em>_include:iterate</em>) are used in order that all the resources that match the <em>_lastUpdated</em> and <em>_type</em> filters will be accompanied, in the result <code>Bundle</code>, with all the other resources which they reference (directly or indirectly).  Note that the use of <em>_include</em> (and <em>_include:iterate</em>) means that a resource may be present in the result <code>Bundle</code> either because it matched the other query parameters or because it was referenced (possibly indirectly) by another resource that matched the other query parameters.</p>
    </li>
    <li>
    <p><em>_filter</em> is used to only get the resources that have been published to a specific <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> of the subscriber organisation.  If the <em>_filter</em> parameter is not present, the operation will return resources that have been published to all of the subscriber organisation's partner services.  The <em>_filter</em> parameter supports the following query expression:</p>
    <ul>
    <li><code>HealthcareService: id eq [FHIR ID of partner service]</code></li>
    </ul>
    </li>
    </ul>
    <p>All of the following query parameters are required in order to receive the complete set of resources that have been created, changed or published to all the subscriber organisation's partner services since <em>[last_synchronized]</em>:</p>
    <p><code>_lastUpdated=[last_synchronized]</code><br/>
    <code>_type=HealthcareService,PractitionerRole,Practitioner,Organization,Location,Provenance,Contract,Task </code><br/>
    <code>_include=Location:organization </code><br/>
    <code>_include=HealthcareService:organization </code><br/>
    <code>_include=HealthcareService:location </code><br/>
    <code>_include=PractitionerRole:organization </code><br/>
    <code>_include=PractitionerRole:location </code><br/>
    <code>_include=PractitionerRole:service </code><br/>
    <code>_include=PractitionerRole:practitioner </code><br/>
    <code>_include=Provenance:target </code><br/>
    <code>_include=Contract:subject </code><br/>
    <code>_include:iterate=HealthcareService:organization  </code><br/>
    <code>_include:iterate=HealthcareService:location </code><br/>
    <code>_include:iterate=PractitionerRole:organization </code><br/>
    <code>_include:iterate=PractitionerRole:location </code><br/>
    <code>_include:iterate=PractitionerRole:service </code><br/>
    <code>_include:iterate=PractitionerRole:practitioner </code></p>
    <p>As described <a href="CapabilityStatement-pca-subscriber-agent.html">above</a> the resources returned in the Bundle exclude any <em>Identifiers</em> (e.g. HPI-Is) that cannot be disclosed to the subscriber.</p>
    <p>This operation supports 'paging' (<a href="https://www.hl7.org/fhir/search.html#Paging">see FHIR specification</a>).  If there are too many resources to return in one <code>Bundle</code>, the FHIR server adds a <em>next</em> link to the response <code>Bundle</code>. The contents of the result <code>Bundle</code> therefore comprise all instances of the requested resource types whose <em>lastUpdated</em> timestamp is greater than the &lt;lastSync&gt; in the request query expression and less than or equal to &lt;lastInBundle&gt; where &lt;lastInBundle&gt; is the greatest <em>lastUpdated</em> value of all resources included in the result <code>Bundle</code>. The Subscriber Agent FHIR server sets the <em>next</em> link to the filter expression that was used in the original request except that &lt;lastSync&gt; is replaced with &lt;lastInBundle&gt;. If the <em>next</em> link is not present in the Bundle, then there are no more service offerings available.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/?[parameters]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>
    <p>Success: <code>Bundle</code> that contains zero to many resources (where the resource type was included in the filter expression of the search request) that conform to the following <a href="profiles.html">PCA profiles</a>:</p>
    <ul>
    <li>
    <p><code>HealthcareService</code> resources conforming to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile</p>
    </li>
    <li>
    <p><code>PractitionerRole</code> resources conforming to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile</p>
    </li>
    <li>
    <p><code>Organization</code> resources conforming to the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile</p>
    </li>
    <li>
    <p><code>Location</code> resources conforming to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile</p>
    </li>
    <li>
    <p><code>Practitioner</code> resources conforming to the <a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a> profile</p>
    </li>
    <li>
    <p><code>Provenance</code> resources conforming to the <a href="StructureDefinition-pca-provenance.html">PCA Provenance</a> profile</p>
    </li>
    <li>
    <p><code>Contract</code> resources conforming to the <a href="StructureDefinition-pca-publication-authorisation-record.html">PCA Publication Authorisation Record</a> profile</p>
    <ul>
    <li><code>Contract</code> resources will be returned that reference each of the <code>HealthcareService</code> or <code>PractitionerRole</code> resources that are included in the <code>Bundle</code> - these <code>Contract</code> resources have a <em>status</em> of “executed” if the associated PCA Partner Service is active, or a <em>status</em> of “cancelled” if the associated PCA Partner Service is inactive).</li>
    <li><code>Contract</code> resources will also be returned that reference <code>HealthcareService</code> or <code>PractitionerRole</code> resources that are not in the <code>Bundle</code> but for which authority to publish has been revoked - these <code>Contract</code> resources will have a <em>status</em> of “revoked”).</li>
    </ul>
    </li>
    <li>
    <p><code>Task</code> resources conforming to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile</p>
    </li>
    </ul>
    </li>
    <li>
    <p>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</p>
    </li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  Search successfully performed (but may return zero matching results).</li>
    <li>Code 400:  The input query could not be parsed, or the <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> referenced in the <code>_filter</code> parameter could not be found or is inactive.</li>
    <li>Code 403:  Server refused to perform the search.</li>
    </ul>
    </div></li></ul></div></div><h3 id="resourcesCap1">Capabilities by Resource/Profile</h3><h4 id="resourcesSummary1">Summary</h4><p>The summary table lists the resources that are part of this configuration, and for each resource it lists:</p><ul><li>The relevant profiles (if any)</li><li>The interactions supported by each resource (<b><span class="bg-info">R</span></b>ead, <b><span class="bg-info">S</span></b>earch, <b><span class="bg-info">U</span></b>pdate, and <b><span class="bg-info">C</span></b>reate, are always shown, while <b><span class="bg-info">VR</span></b>ead, <b><span class="bg-info">P</span></b>atch, <b><span class="bg-info">D</span></b>elete, <b><span class="bg-info">H</span></b>istory on <b><span class="bg-info">I</span></b>nstance, or <b><span class="bg-info">H</span></b>istory on <b><span class="bg-info">T</span></b>ype are only present if at least one of the resources has support for them.</li><li><span>The required, recommended, and some optional search parameters (if any). </span></li><li>The linked resources enabled for <code>_include</code></li><li>The other resources enabled for <code>_revinclude</code></li><li>The operations on the resource (if any)</li></ul><div class="table-responsive"><table class="table table-condensed table-hover"><thead><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th class="text-center"><b title="GET a resource (read interaction)">R</b></th><th class="text-center"><b title="GET all set of resources of the type (search interaction)">S</b></th><th class="text-center"><b title="PUT a new resource version (update interaction)">U</b></th><th class="text-center"><b title="PATCH a new resource version (patch interaction)">P</b></th><th class="text-center"><b title="POST a new resource (create interaction)">C</b></th><th class="text-center"><b title="DELETE a resource (delete interaction)">D</b></th><th><b title="Required and recommended search parameters">Searches</b></th><th><code><b>_include</b></code></th><th><code><b>_revinclude</b></code></th><th><b>Operations</b></th></tr></thead><tbody><tr><td><a href="#Organization1-1">Organization</a></td><td><a href="StructureDefinition-pca-organization.html">http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-organization</a></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td></td><td/><td/><td/></tr><tr><td><a href="#Location1-2">Location</a></td><td><a href="StructureDefinition-pca-location.html">http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-location</a></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td></td><td/><td/><td/></tr><tr><td><a href="#HealthcareService1-3">HealthcareService</a></td><td> </td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center"></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td>_profile, active, organization, service-catgeory, coverage-area.location.address-postalcode</td><td/><td/><td/></tr><tr><td><a href="#PractitionerRole1-4">PractitionerRole</a></td><td><a href="StructureDefinition-pca-practitioner-role.html">http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner-role</a></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td></td><td><code>PractitionerRole:practitioner</code>, <code>PractitionerRole:healthcareService</code>, <code>PractitionerRole:organization</code>, <code>PractitionerRole:location</code></td><td/><td/></tr><tr><td><a href="#Practitioner1-5">Practitioner</a></td><td><a href="StructureDefinition-pca-practitioner.html">http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner</a></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td></td><td/><td/><td/></tr><tr><td><a href="#Provenance1-6">Provenance</a></td><td><a href="StructureDefinition-pca-provenance.html">http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-provenance</a></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td></td><td/><td/><td/></tr><tr><td><a href="#Contract1-7">Contract</a></td><td> </td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td class="text-center"></td><td>_profile, subject, version</td><td/><td/><td/></tr><tr><td><a href="#Task1-8">Task</a></td><td>Supported Profiles<br/>  <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a><br/>  <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a></td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center">y</td><td class="text-center"></td><td>_profile, subject, owner</td><td/><td/><td/></tr><tr><td><a href="#Subscription1-9">Subscription</a></td><td><a href="http://hl7.org/fhir/R4/subscription.html">http://hl7.org/fhir/StructureDefinition/Subscription</a></td><td class="text-center"></td><td class="text-center">y</td><td class="text-center"></td><td class="text-center"></td><td class="text-center">y</td><td class="text-center">y</td><td></td><td/><td/><td/></tr></tbody></table></div><hr/><div class="panel panel-default"><div class="panel-heading"><h4 id="Organization1-1" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Organization</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-6"><span class="lead">Base System Profile</span><br/><a href="StructureDefinition-pca-organization.html">PCA Organization</a></div><div class="col-lg-3"><span class="lead">Profile Conformance</span><br/><b>SHALL</b></div><div class="col-lg-3"><span class="lead">Reference Policy</span><br/></div></div><p/><div class="row"><div class="col-lg-6"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of an <code>Organization</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation retrieves an identified <code>Organization</code> resource that conforms to the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile. As described in the <a href="CapabilityStatement-pca-subscriber-agent.html">common behaviour</a> section, the <code>Organization</code> resource excludes any <em>Identifiers</em> that cannot be disclosed to the subscriber.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Organization/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Organization</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Organization</code> resource that conforms to the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code>Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div><code>patch</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>patch</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#patch">FHIR specification</a>) of an <code>Organization</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to update an identified <code>Organization</code> resource that conforms to the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an <em>identifier</em> element.</p>
    <p>If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:</p>
    <ul>
    <li>The patch document <strong>SHALL</strong> only contain an operation for adding or updating an <em>identifier</em> element.</li>
    <li>Only one <em>identifier</em> element per <em>identifier.system</em> <strong>SHALL</strong> be allowed for the identified <code>Organization</code> resource.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where <em>identifier.system</em> identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where a <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> exists within the PCA service with:
    <ul>
    <li>A <em>status</em> of 'completed', and;</li>
    <li>A <em>focus</em> referencing the <code>Organization</code> resource, and;</li>
    <li>An <em>owner</em> referencing a <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> of the participating organisation associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>PATCH [subscriber agent base url]/Organization/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>A JSON Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc6902">https://datatracker.ietf.org/doc/html/rfc6902</a> with a content type of <code>application/json-patch+json</code>, or;</li>
    <li>An XML Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc5261">https://datatracker.ietf.org/doc/html/rfc5261</a> with a content type of <code>application/xml-patch+xml</code></li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Organization</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Organization</code> resource that conforms to the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    <li>Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-organization.html">PCA Organization</a> profile of the <code>Organization</code> resource type.</p>
    </div></blockquote></div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="Location1-2" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Location</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-6"><span class="lead">Base System Profile</span><br/><a href="StructureDefinition-pca-location.html">PCA Location</a></div><div class="col-lg-3"><span class="lead">Profile Conformance</span><br/><b>SHALL</b></div><div class="col-lg-3"><span class="lead">Reference Policy</span><br/></div></div><p/><div class="row"><div class="col-lg-6"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>Location</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation retrieves an identified <code>Location</code> resource that conforms to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile. As described in the <a href="CapabilityStatement-pca-subscriber-agent.html">common behaviour</a> section, the <code>Location</code> resource excludes any <em>Identifiers</em> that cannot be disclosed to the subscriber.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Location/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Location</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Location</code> resource that conforms to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div><code>patch</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>patch</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#patch">FHIR specification</a>) of a <code>Location</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to update an identified <code>Location</code> resource that conforms to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an <em>identifier</em> element.</p>
    <p>If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:</p>
    <ul>
    <li>The patch document <strong>SHALL</strong> only contain an operation for adding or updating an <em>identifier</em> element.</li>
    <li>Only one <em>identifier</em> element per <em>identifier.system</em> <strong>SHALL</strong> be allowed for the identified <code>Location</code> resource.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where <em>identifier.system</em> identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where a <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> exists within the PCA service with:
    <ul>
    <li>A <em>status</em> of 'completed', and;</li>
    <li>A <em>focus</em> referencing the <code>Location</code> resource, and;</li>
    <li>An <em>owner</em> referencing a <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> of the participating organisation associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>PATCH [subscriber agent base url]/Location/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>A JSON Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc6902">https://datatracker.ietf.org/doc/html/rfc6902</a> with a content type of <code>application/json-patch+json</code>, or;</li>
    <li>An XML Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc5261">https://datatracker.ietf.org/doc/html/rfc5261</a> with a content type of <code>application/xml-patch+xml</code></li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Location</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Location</code> resource that conforms to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    <li>Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile of the <code>Location</code> resource type.</p>
    <p>A <code>Location</code> resource conforming to the <a href="StructureDefinition-pca-location.html">PCA Location</a> profile represents a location at which healthcare services are offered by a PCA publisher.</p>
    </div></blockquote></div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="HealthcareService1-3" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>HealthcareService</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-4"><span class="lead">Core FHIR Resource</span><br/><a href="http://hl7.org/fhir/R4/healthcareservice.html">HealthcareService</a></div><div class="col-lg-4"><span class="lead">Reference Policy</span><br/></div><div class="col-lg-4"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>HealthcareService</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to retrieve an identified <code>HealthcareService</code> resource that conforms to one of the following profiles:</p>
    <ul>
    <li><a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a></li>
    <li><a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a></li>
    </ul>
    <p>As described <a href="CapabilityStatement-pca-subscriber-agent.html">above</a> a <code>HealthcareService</code> resource conforming to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile excludes any <em>Identifiers</em> that cannot be disclosed to the subscriber.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/HealthcareService/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>HealthcareService</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>HealthcareService</code> resource that conforms to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div><code>patch</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>patch</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#patch">FHIR specification</a>) of a <code>HealthcareService</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to update an identified <code>HealthcareService</code> resource that conforms to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an <em>identifier</em> element.</p>
    <p>If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:</p>
    <ul>
    <li>The patch document <strong>SHALL</strong> only contain an operation for adding or updating an <em>identifier</em> element.</li>
    <li>Only one <em>identifier</em> element per <em>identifier.system</em> <strong>SHALL</strong> be allowed for the identified <code>HealthcareService</code> resource.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where <em>identifier.system</em> identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where a <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> exists within the PCA service with:
    <ul>
    <li>A <em>status</em> of 'completed', and;</li>
    <li>A <em>focus</em> referencing the <code>HealthcareService</code> resource, and;</li>
    <li>An <em>owner</em> referencing a <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> of the participating organisation associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>PATCH [subscriber agent base url]/HealthcareService/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>A JSON Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc6902">https://datatracker.ietf.org/doc/html/rfc6902</a> with a content type of <code>application/json-patch+json</code>, or;</li>
    <li>An XML Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc5261">https://datatracker.ietf.org/doc/html/rfc5261</a> with a content type of <code>application/xml-patch+xml</code></li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>HealthcareService</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>HealthcareService</code> resource that conforms to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    <li>Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div><code>search-type</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>search</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#search">FHIR specification</a>) for <code>HealthcareService</code> resources that conform to the <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> profile.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>The operation is used to find <code>HealthcareService</code> resources that that conform to the profile <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> profile and that match the search parameters.<br/>
    Note that all <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> resources in the PCA service are accessible to all authorised client systems.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/HealthcareService/{?[parameters]}</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: Bundle that contains zero to many <code>HealthcareService</code> resources that conform to the <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  Search successfully performed (but may return zero matching results).</li>
    <li>Code 403:  Server refused to perform the search.</li>
    </ul>
    </div></li></ul></div></div><p/><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile and the <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> profile of the <code>HealthcareService</code> resource type.</p>
    <p>A <code>HealthcareService</code> resource conforming to the <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> profile describes a healthcare service offered at a location by a PCA publisher.</p>
    <p>A <code>HealthcareService</code> resource conforming to the <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> profile describes a partner service offered by a subscriber to which PCA publishers can publish their service offerings.</p>
    </div></blockquote></div></div><div class="row"><div class="col-lg-7"><span class="lead">Search Parameters</span><table class="table table-condensed table-hover"><thead><tr><th>Conformance</th><th>Parameter</th><th>Type</th><th>Documentation</th></tr></thead><tbody><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/resource.html#search">_profile</a></td><td><code>uri</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/healthcareservice.html#search">active</a></td><td><code>token</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/healthcareservice.html#search">organization</a></td><td><code>reference</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/healthcareservice.html#search">service-catgeory</a></td><td><code>token</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td>coverage-area.location.address-postalcode</td><td><code>string</code></td><td><div/></td></tr></tbody></table></div><div class="col-lg-5"> </div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="PractitionerRole1-4" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>PractitionerRole</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-6"><span class="lead">Base System Profile</span><br/><a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a></div><div class="col-lg-3"><span class="lead">Profile Conformance</span><br/><b>SHALL</b></div><div class="col-lg-3"><span class="lead">Reference Policy</span><br/></div></div><p/><div class="row"><div class="col-lg-6"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>PractitionerRole</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation retrieves an identified <code>PractitionerRole</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile. As described in the <a href="CapabilityStatement-pca-subscriber-agent.html">common behaviour</a> section, the <code>PractitionerRole</code> resource excludes any <em>Identifiers</em> that cannot be disclosed to the subscriber.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/PractitionerRole/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>PractitionerRole</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>PractitionerRole</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code>Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div><code>patch</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>patch</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#patch">FHIR specification</a>) of a <code>PractitionerRole</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to update an identified <code>PractitionerRole</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an <em>identifier</em> element.</p>
    <p>If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:</p>
    <ul>
    <li>The patch document <strong>SHALL</strong> only contain an operation for adding or updating an <em>identifier</em> element.</li>
    <li>Only one <em>identifier</em> element per <em>identifier.system</em> <strong>SHALL</strong> be allowed for the identified <code>PractitionerRole</code> resource.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where <em>identifier.system</em> identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where a <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> exists within the PCA service with:
    <ul>
    <li>A <em>status</em> of 'completed', and;</li>
    <li>A <em>focus</em> referencing the <code>PractitionerRole</code> resource, and;</li>
    <li>An <em>owner</em> referencing a <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> of the participating organisation associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>PATCH [subscriber agent base url]/PractitionerRole/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>A JSON Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc6902">https://datatracker.ietf.org/doc/html/rfc6902</a> with a content type of <code>application/json-patch+json</code>, or;</li>
    <li>An XML Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc5261">https://datatracker.ietf.org/doc/html/rfc5261</a> with a content type of <code>application/xml-patch+xml</code></li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>PractitionerRole</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>PractitionerRole</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    <li>Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile of the <code>PractitionerRole</code> resource type.<br/>
    Each <code>PractitionerRole</code> resource conforming to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> profile describes a practitioner in a role at a healthcare service.</p>
    </div></blockquote></div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="Practitioner1-5" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Practitioner</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-6"><span class="lead">Base System Profile</span><br/><a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a></div><div class="col-lg-3"><span class="lead">Profile Conformance</span><br/><b>SHALL</b></div><div class="col-lg-3"><span class="lead">Reference Policy</span><br/></div></div><p/><div class="row"><div class="col-lg-6"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>Practitioner</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation retrieves an identified <code>Practitioner</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a> profile. As described in the <a href="CapabilityStatement-pca-subscriber-agent.html">common behaviour</a> section, the <code>Practitioner</code> resource excludes any <em>Identifiers</em> that cannot be disclosed to the subscriber.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Practitioner/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Practitioner</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Practitioner</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a> profile of the <code>Practitioner</code> resource type.</p>
    <p>Each <code>Practitioner</code> resource conforming the <a href="StructureDefinition-pca-practitioner.html">PCA Practitioner</a> profile is a read-only proxy for a corresponding <code>Practitioner</code> resource managed by the PCA portal.</p>
    <p>Each 'proxy' has the same <em>id</em> and <em>versionId</em> as the resource within the PCA portal for which it is a proxy.</p>
    </div></blockquote></div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="Provenance1-6" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Provenance</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-6"><span class="lead">Base System Profile</span><br/><a href="StructureDefinition-pca-provenance.html">PCA Provenance</a></div><div class="col-lg-3"><span class="lead">Profile Conformance</span><br/><b>SHALL</b></div><div class="col-lg-3"><span class="lead">Reference Policy</span><br/></div></div><p/><div class="row"><div class="col-lg-6"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>Provenance</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation retrieves an identified <code>Provenance</code> resource that conforms to the <a href="StructureDefinition-pca-practitioner-role.html">PCA Provenance</a> profile.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Provenance/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Provenance</code> resource that conforms to the <a href="StructureDefinition-pca-provenance.html">PCA Provenance</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-provenance.html">PCA Provenance</a> profile of the <code>Provenance</code> resource type.</p>
    <p>Each <code>Provenance</code> resource conforming to the <a href="StructureDefinition-pca-provenance.html">PCA Provenance</a> profile represents an activity performed by the PCA service (conditionally on behalf of a participating organisation when the target element references a PCA Organization resource) whereby specific data elements of a PCA Organization or PCA Practitioner resource have been initially retrieved, updated or verified from an external system of record.</p>
    </div></blockquote></div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="Contract1-7" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Contract</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-4"><span class="lead">Core FHIR Resource</span><br/><a href="http://hl7.org/fhir/R4/contract.html">Contract</a></div><div class="col-lg-4"><span class="lead">Reference Policy</span><br/></div><div class="col-lg-4"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>Contract</code> resource.</p>
    <p>This operation is used to retrieve an identified <code>Contract</code> resource that conforms to one of the following profiles:</p>
    <ul>
    <li><a href="StructureDefinition-pca-publication-authorisation-record.html">PCA Publication Authorisation Record</a></li>
    <li><a href="StructureDefinition-pca-information-use-statement.html">PCA Information Use Statement</a></li>
    </ul>
    <p>Different authorisation rules apply depending on the profile of the <code>Contract</code> resource being retrieved; see the 'Required OAuth 2.0 scopes' section</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Contract/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Contract</code> resource that conforms to the <a href="StructureDefinition-pca-publication-authorisation-record.html">PCA Publication Authorisation Record</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div><code>search-type</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>search</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#search">FHIR specification</a>) for <code>Contract</code> resources.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to find <code>Contract</code> resources that conform to the <a href="StructureDefinition-pca-information-use-statement.html">PCA Information Use Statement</a> profile and that match the search parameters.</p>
    <p>Note that all <a href="StructureDefinition-pca-information-use-statement.html">PCA Information Use Statement</a> resources in the PCA service are accessible to all authorised client systems.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Contract/{?[parameters]}</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: Bundle containing zero to many <code>Contract</code> resources that conform to the profile <a href="StructureDefinition-pca-information-use-statement.html">PCA Information Use Statement</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  Search successfully performed (but may return zero matching results).</li>
    <li>Code 403:  Server refused to perform the search.</li>
    </ul>
    </div></li></ul></div></div><p/><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-publication-authorisation-record.html">PCA Publication Authorisation Record</a> profile and the <a href="StructureDefinition-pca-information-use-statement.html">PCA Information Use Statement</a> profile of the <code>Contract</code> resource type.</p>
    <p>A <code>Contract</code> resource conforming to the <a href="StructureDefinition-pca-publication-authorisation-record.html">PCA Publication Authorisation Record</a> profile records a decision regarding the publication of a specific service offering (either a <code>HealthcareService</code> or a <code>PractitionerRole</code>) to a specific partner service. The decision is either to authorise publication or to revoke a previous authority to publish.</p>
    <p>A <code>Contract</code> resource conforming to the <a href="StructureDefinition-pca-information-use-statement.html">PCA Information Use Statement</a> profile represents a policy statement by a subscriber organisation's partner service that describes how they will use the information from publisher organisations that is disclosed to the partner service.</p>
    </div></blockquote></div></div><div class="row"><div class="col-lg-7"><span class="lead">Search Parameters</span><table class="table table-condensed table-hover"><thead><tr><th>Conformance</th><th>Parameter</th><th>Type</th><th>Documentation</th></tr></thead><tbody><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/resource.html#search">_profile</a></td><td><code>uri</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/contract.html#search">subject</a></td><td><code>reference</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td>version</td><td><code>string</code></td><td><div/></td></tr></tbody></table></div><div class="col-lg-5"> </div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="Task1-8" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Task</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-4"><span class="lead">Core FHIR Resource</span><br/><a href="http://hl7.org/fhir/R4/task.html">Task</a></div><div class="col-lg-4"><span class="lead">Reference Policy</span><br/></div><div class="col-lg-4"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>read</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>read</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#read">FHIR specification</a>) of a <code>Task</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation retrieves an identified <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service</a> profile of the Task resource type.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Task/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain one of the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    <li><code> Organization/[id]:SS_TaskManager</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.<br/>
    The <code>SS_Updater</code> role <strong>SHALL</strong> be used for reading <code>Task</code>resources conforming to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.<br/>
    The <code>SS_TaskManager</code> role <strong>SHALL</strong> be used for reading <code>Task</code>resources conforming to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div><code>create</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>create</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#create">FHIR specification</a>) of a <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>If any of the applicable data validation rules are violated in the input resource then the request is rejected and the error code 422 is returned.</p>
    <p><em>Common validation rules:</em></p>
    <ul>
    <li>The resource <strong>SHALL</strong> conform to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service</a> profile.</li>
    <li><em>id</em> <strong>SHALL NOT</strong> be present.</li>
    <li><em>meta.versionId</em> <strong>SHALL NOT</strong> be present.</li>
    <li><em>meta.lastUpdated</em> <strong>SHALL NOT</strong> be present.</li>
    <li><em>focus</em> <strong>SHALL</strong> reference a resource that has been published to one or more <a href="StructureDefinition-pca-partner-service.html">Partner Services</a> associated with the target PCA Subscriber Agent.</li>
    </ul>
    <p><em>PCA Match Record validation rules:</em></p>
    <ul>
    <li>If the resource conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile:
    <ul>
    <li><em>note.text</em> <strong>SHALL</strong> be a maximum of 200 characters.</li>
    <li><em>owner</em> <strong>SHALL</strong> reference a <a href="StructureDefinition-pca-partner-service.html">Partner Service</a> associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    </ul>
    <p><em>PCA Partner Service Task validation rules:</em></p>
    <ul>
    <li>
    <p>If the resource conforms to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile:</p>
    <ul>
    <li><em>for</em> <strong>SHALL</strong> reference a <a href="StructureDefinition-pca-partner-service.html">Partner Service</a> associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    <li>
    <p>If the resource conforms to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile and the <code>type</code> is 'PartnerServiceCompleteOnlineForm':</p>
    <ul>
    <li><em>focus</em> <strong>SHALL</strong> reference either a <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> or <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> resource.</li>
    <li>The resource <strong>SHALL</strong> contain <em>input</em> elements for each of the following task parameters:
    <ul>
    <li><code>type</code> = 'dueOn', <code>value</code> = valueDateTime</li>
    <li><code>type</code> = 'reason', <code>value</code> = valueString</li>
    <li><code>type</code> = 'urlId', <code>value</code> = valueString</li>
    <li><code>type</code> = 'formName', <code>value</code> = valueString</li>
    </ul>
    </li>
    <li>The 'urlId' task paramater <em><strong>SHALL</strong></em> match one of the partner service website records (configured in PCA) of the <a href="StructureDefinition-pca-partner-service.html">Partner Service</a> identified by <em>owner</em>.</li>
    <li>The partner service website record identified by the 'urlId' task paramater <em><strong>SHALL</strong></em> have a context of use (e.g. Healthcare Service context or Practitioner Role context) that aligns with the resource type referenced in the <em>focus</em> element.</li>
    </ul>
    </li>
    </ul>
    <hr/>
    <ul>
    <li>If the resource conforms to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile and the <code>type</code> is 'PartnerServiceProvideMissingInformation':
    <ul>
    <li>The resource <strong>SHALL</strong> contain an <em>input</em> element for the following task parameter:
    <ul>
    <li><code>type</code> = 'missingDetails', <code>value</code> = valueString</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-organization.html">PCA Organization</a> resource, the 'missingDetails' task parameter <strong>SHALL</strong> contain a comma-separated string containing one or more of the following property names:
    <ul>
    <li>Fax</li>
    <li>Website</li>
    <li>PostalAddress</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-location.html">PCA Location</a> resource, the 'missingDetails' task parameter <strong>SHALL</strong> contain a comma-separated string containing one or more of the following property names:
    <ul>
    <li>Phone</li>
    <li>Email</li>
    <li>Fax</li>
    <li>Website</li>
    <li>PostalAddress</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> resource, the 'missingDetails' task parameter <strong>SHALL</strong> contain a comma-separated string containing one or more of the following property names:
    <ul>
    <li>Phone</li>
    <li>Email</li>
    <li>Fax</li>
    <li>AfterHoursPhone</li>
    <li>Website</li>
    <li>PostalAddress</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> resource, the 'missingDetails' task parameter <strong>SHALL</strong> contain a comma-separated string containing one or more of the following property names:
    <ul>
    <li>PreferredNameAtLocation</li>
    <li>NumberOfDays</li>
    <li>HpiiIdentifier</li>
    <li>MedicareProviderNumber</li>
    </ul>
    </li>
    </ul>
    </li>
    </ul>
    <hr/>
    <ul>
    <li>If the resource conforms to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile and the <code>type</code> is 'PartnerServiceVerifyInformation':
    <ul>
    <li>The resource <strong>SHALL</strong> contain one <em>input</em> element for the following task parameter:
    <ul>
    <li><code>type</code> = 'verifyDetails', <code>value</code> = valueString</li>
    </ul>
    </li>
    <li>The <em>input</em> element <strong>SHALL</strong> use the <a href="StructureDefinition-pca-property-name.html">PCA Property Name</a> extension to identify the property name:
    <ul>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-organization.html">PCA Organization</a> resource, the extension <strong>SHALL</strong> use one of the following property names:
    <ul>
    <li>Fax</li>
    <li>Website</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-location.html">PCA Location</a> resource, the extension <strong>SHALL</strong> use one of the following property      names:
    <ul>
    <li>Phone</li>
    <li>Email</li>
    <li>Fax</li>
    <li>Website</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-healthcare-service.html">PCA Healthcare Service</a> resource, the extension <strong>SHALL</strong> use one of the following property names:
    <ul>
    <li>Phone</li>
    <li>Email</li>
    <li>Fax</li>
    <li>AfterHoursPhone</li>
    <li>Website</li>
    </ul>
    </li>
    <li>If <em>focus</em> references a <a href="StructureDefinition-pca-practitioner-role.html">PCA Practitioner Role</a> resource, the extension <strong>SHALL</strong> use one of the following property names:
    <ul>
    <li>PreferredNameAtLocation</li>
    <li>NumberOfDays</li>
    </ul>
    </li>
    </ul>
    </li>
    <li>The <em>input</em> element <strong>SHALL</strong> use valueString to record a new suggested value of the property, if the Partner Service chooses to suggest a new value.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>POST [subscriber agent base url]/Task</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li><code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the new <code>Task</code> resource.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    <li><code> Organization/[id]:SS_TaskManager</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.<br/>
    The <code>SS_Updater</code> role <strong>SHALL</strong> be used for creating <code>Task</code> resources conforming to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.<br/>
    The <code>SS_TaskManager</code> role <strong>SHALL</strong> be used for creating <code>Task</code> resources conforming to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 201:  The resource was successfully created.</li>
    <li>Code 400:  The input resource could not be parsed or failed basic FHIR validation rules.</li>
    <li>Code 404:  The resource type is not supported, or not a FHIR end-point.</li>
    <li>Code 422:  The input resource violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div><code>update</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>update</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#update">FHIR specification</a>) of a <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>If the 'if-match' HTTP header is not provided in the request, then the PCA Subscriber Agent will reject the request and return the error code 400.</p>
    <p>If the 'if-match' HTTP header does not match the current version, then the PCA Subscriber Agent will reject the request and return the error code 412.</p>
    <p>If any of the applicable data validation rules are violated in the input resource then the request is rejected and the error code 422 is returned.</p>
    <p><em>Common validation rules:</em></p>
    <ul>
    <li>The resource <strong>SHALL</strong> conform to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</li>
    <li><em>id</em> <strong>SHALL</strong> be identical to the corresponding value in the version of the <code>Task</code> identified in the 'if-match' HTTP header.</li>
    <li><em>meta.versionId</em> <strong>SHALL NOT</strong> be present.</li>
    <li><em>meta.lastUpdated</em> <strong>SHALL NOT</strong> be present.</li>
    </ul>
    <p><em>PCA Match Record validation rules:</em></p>
    <ul>
    <li>If the resource conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile:
    <ul>
    <li><em>owner</em> <strong>SHALL</strong> reference a <a href="StructureDefinition-pca-partner-service.html">Partner Service</a> associated with the target PCA Subscriber Agent.</li>
    <li>Only changes to <em>status</em> (and optionally <em>note.text</em>) will be accepted; changes to any other element values will not be accepted when updating an existing <code>Task</code>.</li>
    <li><em>note.text</em> <strong>SHALL</strong> only be updated if <em>status</em> is being changed from 'completed' to 'failed'.</li>
    <li><em>note.text</em> <strong>SHALL</strong> be a maximum of 200 characters.</li>
    </ul>
    </li>
    </ul>
    <p><em>PCA Partner Service Task validation rules:</em></p>
    <ul>
    <li>If the resource conforms to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile:
    <ul>
    <li><em>for</em> <strong>SHALL</strong> reference a <a href="StructureDefinition-pca-partner-service.html">Partner Service</a> associated with the target PCA Subscriber Agent.</li>
    <li><em>type</em> <strong>SHALL</strong> be 'PartnerServiceCompleteOnlineForm'.</li>
    <li>Only a change to <em>status</em> from 'requested' to 'completed' will be accepted; changes to any other element values will not be accepted when updating an existing <code>Task</code>.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>PUT [subscriber agent base url]/Task/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    <li><code>if-match [version id]</code> where [version id] is the version of the <code>Task</code> being updated.</li>
    </ul>
    <p><strong>Request Body</strong>:<br/>
    <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.</p>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Task</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    <li><code> Organization/[id]:SS_TaskManager</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.<br/>
    The <code>SS_Updater</code> role <strong>SHALL</strong> be used for updating <code>Task</code> resources conforming to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.<br/>
    The <code>SS_TaskManager</code> role <strong>SHALL</strong> be used for updating <code>Task</code> resources conforming to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 400:  Client error:  request did not include the <em>if-match</em> HTTP header.</li>
    <li>Code 404:  The resource was not found.</li>
    <li>Code 412:  The version id given in the <em>if-Match</em> HTTP request header does not match the current version.</li>
    <li>Code 422:  The input resource violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div><code>patch</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>patch</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#patch">FHIR specification</a>) of a <code>Task</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to update an identified <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an <em>identifier</em> element.</p>
    <p>If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:</p>
    <ul>
    <li>The patch document <strong>SHALL</strong> only contain an operation for adding or updating an <em>identifier</em> element.</li>
    <li>Only one <em>identifier</em> element per <em>identifier.system</em> <strong>SHALL</strong> be allowed for the identified <code>Task</code> resource.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where <em>identifier.system</em> identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.</li>
    <li>The patch operation <strong>SHALL</strong> only add or update an <em>identifier</em> element where a <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> exists within the PCA service with:
    <ul>
    <li>A <em>status</em> of 'completed', and;</li>
    <li>A <em>focus</em> referencing the <code>Task</code> resource, and;</li>
    <li>An <em>owner</em> referencing a <a href="StructureDefinition-pca-partner-service.html">PCA Partner Service</a> of the participating organisation associated with the target PCA Subscriber Agent.</li>
    </ul>
    </li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>PATCH [subscriber agent base url]/Task/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/json-patch+json;charset=utf-8</code> or <code>Accept: application/xml-patch+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>A JSON Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc6902">https://datatracker.ietf.org/doc/html/rfc6902</a> with a content type of <code>application/json-patch+json</code>, or;</li>
    <li>An XML Patch document that conforms to <a href="https://datatracker.ietf.org/doc/html/rfc5261">https://datatracker.ietf.org/doc/html/rfc5261</a> with a content type of <code>application/xml-patch+xml</code></li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>ETag: [version id]</code> where [version id] identifies the version of the <code>Task</code> resource returned.</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Task</code> resource that conforms to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Updater</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  The resource was found and returned.</li>
    <li>Code 404:  The resource was not found.</li>
    <li>Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div><code>search-type</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>search</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#search">FHIR specification</a>) for <code>Task</code> resources that conform to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>The operation is used to find <code>Task</code> resources that that conform to the profile <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile and that match the search parameters.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Task/{?[parameters]}</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: Bundle that contains zero to many <code>Task</code> resources that conform to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  Search successfully performed (but may return zero matching results).</li>
    <li>Code 403:  Server refused to perform the search.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-6"><span class="lead">Supported Profiles</span><p><a href="StructureDefinition-pca-match-record.html">PCA Match Record</a><br/><a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a></p></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile or the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service Task</a> profile of the <code>Task</code> resource type.</p>
    <p>A <code>Task</code> resource conforming to the <a href="StructureDefinition-pca-match-record.html">PCA Match Record</a> profile indicates the matching status of a service offering to a partner service’s local data store.</p>
    <p>A <code>Task</code> resource conforming to the <a href="StructureDefinition-pca-partner-service-task.html">PCA Partner Service  Task</a> profile indicates a task created by a partner service via their authorised subscribing system.</p>
    </div></blockquote></div></div><div class="row"><div class="col-lg-7"><span class="lead">Search Parameters</span><table class="table table-condensed table-hover"><thead><tr><th>Conformance</th><th>Parameter</th><th>Type</th><th>Documentation</th></tr></thead><tbody><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/resource.html#search">_profile</a></td><td><code>uri</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/task.html#search">subject</a></td><td><code>reference</code></td><td><div/></td></tr><tr><td><b>SHALL</b></td><td><a href="http://hl7.org/fhir/R4/task.html#search">owner</a></td><td><code>reference</code></td><td><div/></td></tr></tbody></table></div><div class="col-lg-5"> </div></div></div></div></div><div class="panel panel-default"><div class="panel-heading"><h4 id="Subscription1-9" class="panel-title"><span style="float: right;">Resource Conformance: supported </span>Subscription</h4></div><div class="panel-body"><div class="container"><div class="row"><div class="col-lg-6"><span class="lead">Base System Profile</span><br/><a href="http://hl7.org/fhir/R4/subscription.html">Subscription</a></div><div class="col-lg-3"><span class="lead">Profile Conformance</span><br/><b>SHALL</b></div><div class="col-lg-3"><span class="lead">Reference Policy</span><br/></div></div><p/><div class="row"><div class="col-lg-6"><span class="lead">Interaction summary</span><br/><ul><li>Supports <br/><code>create</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>create</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#create">FHIR specification</a>) of a <code>Subscription</code> resource conforming to the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to register a callback to receive a notification whenever there are changes in the data set that is published to a subscriber.</p>
    <p>A notification is simply a HTTP POST without any content – the purpose is to trigger the subscriber’s client system to get the available service offerings by invoking the <a href="CapabilityStatement-pca-subscriber-agent.html#search-system">whole system search operation</a>.</p>
    <p>If any of the following data validation rules are violated in the input resource, then the request is rejected and the error code 422 is returned:</p>
    <ul>
    <li><em>status</em> <strong>SHALL</strong> be 'requested'</li>
    <li><em>reason</em> <strong>SHALL</strong> be 'subscriber change notifications'</li>
    <li><em>criteria</em>  <strong>SHALL</strong> be a space separated list of resource types from the list 'HealthcareService', 'PractitionerRole', 'Location', 'Organization', 'Practitioner', 'Provenance', 'Contract', 'Task'</li>
    <li><em>channel.type</em>  <strong>SHALL</strong> be 'rest-hook'</li>
    <li><em>channel.endpoint</em> <strong>SHALL</strong> be the URL of an endpoint that is operated by (or on behalf of) the subscriber for receiving notifications. The protocol <strong>SHALL</strong> be https.</li>
    <li><em>channel.payload</em> <strong>SHALL NOT</strong> be present – its absence indicates that the subscriber will not receive any resources via this endpoint.</li>
    <li><em>channel.header</em> <strong>SHALL</strong> be set to 'Authorization: Bearer [secret string]' where [secret string] is the basic authentication string, set by the subscriber organisation, that is used to authenticate the PCA Subscriber Agent to the notification receiving endpoint.</li>
    </ul>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>POST [subscriber agent base url]/Subscription</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li><code>Subscription</code> resource that conforms to the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile.</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Subcription</code> resource that conforms to the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 201:  The resource was successfully created.</li>
    <li>Code 400:  The input resource could not be parsed or failed basic FHIR validation rules.</li>
    <li>Code 404:  The resource type is not supported, or not a FHIR end-point.</li>
    <li>Code 422:  The input resource violated applicable FHIR profiles or server data validation rules.</li>
    </ul>
    </div><code>search-type</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>search</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#search">FHIR specification</a>) for a <code>Subscription</code> resource that is associated with the target Subscriber Agent and that conforms to the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to find a <code>Subscription</code> resource that is associated with the target Subscriber Agent and that conforms to the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>GET [subscriber agent base url]/Subscription/</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Accept: application/fhir+json;charset=utf-8</code> or <code>Accept: application/fhir+xml;charset=utf-8</code></li>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li><code>Content-Type: application/fhir+json;charset=utf-8</code> or <code>Content-Type: application/fhir+xml;charset=utf-8</code></li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>Success: <code>Bundle</code> that contains zero or one <code>Subscription</code> resource that that is associated with the target Subscriber Agent and that conforms to the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile.</li>
    <li>Error: <code>OperationOutcome</code> resource (see <a href="https://www.hl7.org/fhir/operationoutcome.html">FHIR specification</a>).</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 200:  Search successfully performed (but may return zero matching results).</li>
    <li>Code 403:  Server refused to perform the search.</li>
    </ul>
    </div><code>delete</code><div><p><strong>Definition</strong>:</p>
    <p>This operation is a RESTful <strong>delete</strong> interaction (as described in the <a href="https://www.hl7.org/fhir/http.html#delete">FHIR specification</a>) of a <code>Subscription</code> resource.</p>
    <p><strong>Behaviour</strong>:</p>
    <p>This operation is used to deregister an existing notification callback.</p>
    <p><strong>HTTP interaction signature</strong>:</p>
    <ul>
    <li><code>DELETE [subscriber agent base url]/Subscription/[id]</code></li>
    </ul>
    <p><strong>Mandatory Request Headers</strong>:</p>
    <ul>
    <li><code>Authorization: Bearer [token]</code></li>
    </ul>
    <p><strong>Request Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Mandatory Response Headers</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Response Body</strong>:</p>
    <ul>
    <li>(No request body)</li>
    </ul>
    <p><strong>Required OAuth 2.0 scopes</strong>:</p>
    <p>The <em>scope</em> string <strong>SHALL</strong> contain the following <em>scoped role</em>:</p>
    <ul>
    <li><code> Organization/[id]:SS_Receiver</code></li>
    </ul>
    <p>Where [id] <strong>SHALL</strong> identify the <code>Organization</code> associated with the target PCA Subscriber Agent.</p>
    <p><strong>Response Codes</strong>:</p>
    <ul>
    <li>Code 202:  The deletion was accepted.</li>
    <li>Code 404:  The resource was not found.</li>
    </ul>
    </div></li></ul></div></div><p/><div class="row"><div class="col-12"><span class="lead">Documentation</span><blockquote><div><p>This section defines the supported interactions for the <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile of the <code>Subscription</code> resource type.</p>
    <p>The <a href="StructureDefinition-pca-subscription.html">PCA Subscription</a> profile of <code>Subscription</code> is used by subscribing systems to register for notifications from the PCA service when new or updated service offerings are available, or when publication of existing service offerings has been newly revoked.</p>
    </div></blockquote></div></div></div></div></div></div>
      </text>
      <url
           value="http://pca.digitalhealth.gov.au/fhir/4.0/CapabilityStatement/pca-subscriber-agent"/>
      <version value="24.2.0.0"/>
      <name value="PCASubscriberAgentCapabilityStatement"/>
      <title value="PCA Subscriber Agent Capability Statement"/>
      <status value="active"/>
      <experimental value="false"/>
      <date value="2024-09-23T10:57:22+10:00"/>
      <publisher value="Australian Digital Health Agency"/>
      <contact>
        <telecom>
          <system value="email"/>
          <value value="mailto:help@digitalhealth.gov.au"/>
        </telecom>
      </contact>
      <description
                   value="This is the Capability statement for a PCA Subscriber Agent FHIR server."/>
      <jurisdiction>
        <coding>
          <system value="urn:iso:std:iso:3166"/>
          <code value="AU"/>
        </coding>
      </jurisdiction>
      <copyright
                 value="Copyright © 2024 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/."/>
      <kind value="requirements"/>
      <fhirVersion value="4.0.1"/>
      <format value="application/fhir+json"/>
      <format value="application/fhir+xml"/>
      <rest>
        <mode value="server"/>
        <documentation
                       value="A PCA Subscriber Agent manages the service offerings for one subscriber organisation (also referred to as a 'business partner' in the PCA portal).

    The PCA service instantiates one PCA Subscriber Agent for each participating subscriber organisation. That is, each subscriber organisation interacts with a PCA Subscriber Agent located at a *subscriber agent base url* that is unique to that organisation.

    The *subscriber agent base URL* for a particular organisation is available via the PCA portal on the 'Organisation Details' screen of the subscriber organisation.

    A service offering is made available to a subscriber organisation when a publisher authorises publication of a resource to one or more of the subscriber organisation's partner services.

     **Publication process**

     A PCA Publisher Agent creates the ```Location```, ```HealthcareService``` and ```PractitionerRole``` resources (that are associated with existing ```Organization``` and ```Practitioner``` resources) that represent their service offerings.  These resources are made available to a subscriber organisation when a publisher authorises publication of a ```HealthcareService``` or ```PractitionerRole``` resource to one or more of the subscriber organisation's partner services.

     The authority to publish is represented using ```Contract``` resources which are also implemented by the PCA Publisher Agent (see the [Contract resource endpoint](CapabilityStatement-pca-publisher-agent.html#contract)).

     **Identifier disclosure rules**

     The PCA service enforces certain business rules regarding the disclosure of *Identifiers* (including subscriber-issued identifiers) in the resources that it makes available to subscribers.

     The result of these rules may be that a copy of  a resource received by one subscriber may contain *Identifiers* that are not included in the copy of the same resource that is received by a different subscriber.

     In the case of HPI-Is these *identifier disclosure rules* ensure that relevant legal requirements are complied with.

     Other *identifier disclosure rules* are defined by the PCA operator.

     The *identifier disclosure rules* are applied automatically at the time that the resource is retrieved by the target PCA Subscriber Agent.

     **Authorisation rules**

    Authorised client systems are only permitted to interact with a PCA Subscriber Agent API where the participating organisation associated with the PCA Subscriber Agent has a subscriber approval status of 'Approved'.

     **Resource profiles and extensions**

    This API specification defines the required resource profiles for each operation.  The PCA Subscriber Agent will reject any request to create or update a resource that contains any extensions (including modifier extensions) not explicitly defined in that resource profile.
        "/>
        <security>
          <cors value="true"/>
          <service>
            <coding>
              <system
                      value="http://terminology.hl7.org/CodeSystem/restful-security-service"/>
              <code value="OAuth"/>
              <display value="OAuth"/>
            </coding>
          </service>
          <description value="This server implements OAuth2"/>
        </security>
        <resource>
          <type value="Organization"/>
          <profile
                   value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-organization"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Organization](StructureDefinition-pca-organization.html) profile of the ```Organization``` resource type.     "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of an ```Organization``` resource.

     **Behaviour**:

     This operation retrieves an identified ```Organization``` resource that conforms to the [PCA Organization](StructureDefinition-pca-organization.html) profile. As described in the [common behaviour](CapabilityStatement-pca-subscriber-agent.html) section, the ```Organization``` resource excludes any *Identifiers* that cannot be disclosed to the subscriber.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Organization/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Organization``` resource returned.

     **Response Body**:
     * Success: ```Organization``` resource that conforms to the [PCA Organization](StructureDefinition-pca-organization.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ```Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.      "/>
          </interaction>
          <interaction>
            <code value="patch"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **patch** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#patch)) of an ```Organization``` resource.

     **Behaviour**:

     This operation is used to update an identified ```Organization``` resource that conforms to the [PCA Organization](StructureDefinition-pca-organization.html) profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an *identifier* element.

     If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:

     * The patch document **SHALL** only contain an operation for adding or updating an *identifier* element.
     * Only one *identifier* element per *identifier.system* **SHALL** be allowed for the identified ```Organization``` resource.
     * The patch operation **SHALL** only add or update an *identifier* element where *identifier.system* identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.
     * The patch operation **SHALL** only add or update an *identifier* element where a [PCA Match Record](StructureDefinition-pca-match-record.html) exists within the PCA service with:
       * A *status* of 'completed', and;
       * A *focus* referencing the ```Organization``` resource, and;
       * An *owner* referencing a [PCA Partner Service](StructureDefinition-pca-partner-service.html) of the participating organisation associated with the target PCA Subscriber Agent.

     **HTTP interaction signature**:
     * ```PATCH [subscriber agent base url]/Organization/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Content-Type: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * A JSON Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc6902](https://datatracker.ietf.org/doc/html/rfc6902) with a content type of ```application/json-patch+json```, or;
     * An XML Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc5261](https://datatracker.ietf.org/doc/html/rfc5261) with a content type of ```application/xml-patch+xml```

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Organization``` resource returned.

     **Response Body**:
     * Success: ```Organization``` resource that conforms to the [PCA Organization](StructureDefinition-pca-organization.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.
     *  Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <versioning value="versioned"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
        </resource>
        <resource>
          <type value="Location"/>
          <profile
                   value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-location"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Location](StructureDefinition-pca-location.html) profile of the ```Location``` resource type.

     A ```Location``` resource conforming to the [PCA Location](StructureDefinition-pca-location.html) profile represents a location at which healthcare services are offered by a PCA publisher.       "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```Location``` resource.

     **Behaviour**:

     This operation retrieves an identified ```Location``` resource that conforms to the [PCA Location](StructureDefinition-pca-location.html) profile. As described in the [common behaviour](CapabilityStatement-pca-subscriber-agent.html) section, the ```Location``` resource excludes any *Identifiers* that cannot be disclosed to the subscriber.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Location/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Location``` resource returned.

     **Response Body**:
     * Success: ```Location``` resource that conforms to the [PCA Location](StructureDefinition-pca-location.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.      "/>
          </interaction>
          <interaction>
            <code value="patch"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **patch** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#patch)) of a ```Location``` resource.

     **Behaviour**:

     This operation is used to update an identified ```Location``` resource that conforms to the [PCA Location](StructureDefinition-pca-location.html) profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an *identifier* element.

     If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:

     * The patch document **SHALL** only contain an operation for adding or updating an *identifier* element.
     * Only one *identifier* element per *identifier.system* **SHALL** be allowed for the identified ```Location``` resource.
     * The patch operation **SHALL** only add or update an *identifier* element where *identifier.system* identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.
     * The patch operation **SHALL** only add or update an *identifier* element where a [PCA Match Record](StructureDefinition-pca-match-record.html) exists within the PCA service with:
       * A *status* of 'completed', and;
       * A *focus* referencing the ```Location``` resource, and;
       * An *owner* referencing a [PCA Partner Service](StructureDefinition-pca-partner-service.html) of the participating organisation associated with the target PCA Subscriber Agent.

     **HTTP interaction signature**:
     * ```PATCH [subscriber agent base url]/Location/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Content-Type: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * A JSON Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc6902](https://datatracker.ietf.org/doc/html/rfc6902) with a content type of ```application/json-patch+json```, or;
     * An XML Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc5261](https://datatracker.ietf.org/doc/html/rfc5261) with a content type of ```application/xml-patch+xml```

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Location``` resource returned.

     **Response Body**:
     * Success: ```Location``` resource that conforms to the [PCA Location](StructureDefinition-pca-location.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.
     *  Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <versioning value="versioned"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
        </resource>
        <resource>
          <type value="HealthcareService"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile and the [PCA Partner Service](StructureDefinition-pca-partner-service.html) profile of the ```HealthcareService``` resource type.

     A ```HealthcareService``` resource conforming to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile describes a healthcare service offered at a location by a PCA publisher.

     A ```HealthcareService``` resource conforming to the [PCA Partner Service](StructureDefinition-pca-partner-service.html) profile describes a partner service offered by a subscriber to which PCA publishers can publish their service offerings.     "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```HealthcareService``` resource.

     **Behaviour**:

     This operation is used to retrieve an identified ```HealthcareService``` resource that conforms to one of the following profiles:
     * [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html)
     * [PCA Partner Service](StructureDefinition-pca-partner-service.html)

     As described [above](CapabilityStatement-pca-subscriber-agent.html) a ```HealthcareService``` resource conforming to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile excludes any *Identifiers* that cannot be disclosed to the subscriber.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/HealthcareService/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```HealthcareService``` resource returned.

     **Response Body**:
     * Success: ```HealthcareService``` resource that conforms to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  The resource was found and returned.
     * Code 404:  The resource was not found.      "/>
          </interaction>
          <interaction>
            <code value="patch"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **patch** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#patch)) of a ```HealthcareService``` resource.

     **Behaviour**:

     This operation is used to update an identified ```HealthcareService``` resource that conforms to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an *identifier* element.

     If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:

     * The patch document **SHALL** only contain an operation for adding or updating an *identifier* element.
     * Only one *identifier* element per *identifier.system* **SHALL** be allowed for the identified ```HealthcareService``` resource.
     * The patch operation **SHALL** only add or update an *identifier* element where *identifier.system* identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.
     * The patch operation **SHALL** only add or update an *identifier* element where a [PCA Match Record](StructureDefinition-pca-match-record.html) exists within the PCA service with:
       * A *status* of 'completed', and;
       * A *focus* referencing the ```HealthcareService``` resource, and;
       * An *owner* referencing a [PCA Partner Service](StructureDefinition-pca-partner-service.html) of the participating organisation associated with the target PCA Subscriber Agent.

     **HTTP interaction signature**:
     * ```PATCH [subscriber agent base url]/HealthcareService/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Content-Type: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * A JSON Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc6902](https://datatracker.ietf.org/doc/html/rfc6902) with a content type of ```application/json-patch+json```, or;
     * An XML Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc5261](https://datatracker.ietf.org/doc/html/rfc5261) with a content type of ```application/xml-patch+xml```

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```HealthcareService``` resource returned.

     **Response Body**:
     * Success: ```HealthcareService``` resource that conforms to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.
     *  Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <interaction>
            <code value="search-type"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **search** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#search)) for ```HealthcareService``` resources that conform to the [PCA Partner Service](StructureDefinition-pca-partner-service.html) profile.

     **Behaviour**:

     The operation is used to find ```HealthcareService``` resources that that conform to the profile [PCA Partner Service](StructureDefinition-pca-partner-service.html) profile and that match the search parameters.
     Note that all [PCA Partner Service](StructureDefinition-pca-partner-service.html) resources in the PCA service are accessible to all authorised client systems.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/HealthcareService/{?[parameters]}```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: Bundle that contains zero to many ```HealthcareService``` resources that conform to the [PCA Partner Service](StructureDefinition-pca-partner-service.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  Search successfully performed (but may return zero matching results).
     * Code 403:  Server refused to perform the search.      "/>
          </interaction>
          <versioning value="versioned"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
          <searchParam>
            <name value="_profile"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/Resource-profile"/>
            <type value="uri"/>
          </searchParam>
          <searchParam>
            <name value="active"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/HealthcareService-active"/>
            <type value="token"/>
          </searchParam>
          <searchParam>
            <name value="organization"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/HealthcareService-organization"/>
            <type value="reference"/>
          </searchParam>
          <searchParam>
            <name value="service-catgeory"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/HealthcareService-service-category"/>
            <type value="token"/>
          </searchParam>
          <searchParam>
            <name value="coverage-area.location.address-postalcode"/>
            <type value="string"/>
          </searchParam>
        </resource>
        <resource>
          <type value="PractitionerRole"/>
          <profile
                   value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner-role"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile of the ```PractitionerRole``` resource type.
    Each ```PractitionerRole``` resource conforming to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile describes a practitioner in a role at a healthcare service.     "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```PractitionerRole``` resource.

     **Behaviour**:

     This operation retrieves an identified ```PractitionerRole``` resource that conforms to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile. As described in the [common behaviour](CapabilityStatement-pca-subscriber-agent.html) section, the ```PractitionerRole``` resource excludes any *Identifiers* that cannot be disclosed to the subscriber.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/PractitionerRole/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```PractitionerRole``` resource returned.

     **Response Body**:
     * Success: ```PractitionerRole``` resource that conforms to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ```Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
    *  Code 200:  The resource was found and returned.
    *  Code 404:  The resource was not found.      "/>
          </interaction>
          <interaction>
            <code value="patch"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **patch** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#patch)) of a ```PractitionerRole``` resource.

     **Behaviour**:

     This operation is used to update an identified ```PractitionerRole``` resource that conforms to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an *identifier* element.

     If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:

     * The patch document **SHALL** only contain an operation for adding or updating an *identifier* element.
     * Only one *identifier* element per *identifier.system* **SHALL** be allowed for the identified ```PractitionerRole``` resource.
     * The patch operation **SHALL** only add or update an *identifier* element where *identifier.system* identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.
     * The patch operation **SHALL** only add or update an *identifier* element where a [PCA Match Record](StructureDefinition-pca-match-record.html) exists within the PCA service with:
       * A *status* of 'completed', and;
       * A *focus* referencing the ```PractitionerRole``` resource, and;
       * An *owner* referencing a [PCA Partner Service](StructureDefinition-pca-partner-service.html) of the participating organisation associated with the target PCA Subscriber Agent.

     **HTTP interaction signature**:
     * ```PATCH [subscriber agent base url]/PractitionerRole/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Content-Type: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * A JSON Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc6902](https://datatracker.ietf.org/doc/html/rfc6902) with a content type of ```application/json-patch+json```, or;
     * An XML Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc5261](https://datatracker.ietf.org/doc/html/rfc5261) with a content type of ```application/xml-patch+xml```

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```PractitionerRole``` resource returned.

     **Response Body**:
     * Success: ```PractitionerRole``` resource that conforms to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.
     *  Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <versioning value="versioned"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
          <searchInclude value="PractitionerRole:practitioner"/>
          <searchInclude value="PractitionerRole:healthcareService"/>
          <searchInclude value="PractitionerRole:organization"/>
          <searchInclude value="PractitionerRole:location"/>
        </resource>
        <resource>
          <type value="Practitioner"/>
          <profile
                   value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Practitioner](StructureDefinition-pca-practitioner.html) profile of the ```Practitioner``` resource type.

    Each ```Practitioner``` resource conforming the [PCA Practitioner](StructureDefinition-pca-practitioner.html) profile is a read-only proxy for a corresponding ```Practitioner``` resource managed by the PCA portal.

    Each 'proxy' has the same *id* and *versionId* as the resource within the PCA portal for which it is a proxy.       "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```Practitioner``` resource.

     **Behaviour**:

     This operation retrieves an identified ```Practitioner``` resource that conforms to the [PCA Practitioner](StructureDefinition-pca-practitioner.html) profile. As described in the [common behaviour](CapabilityStatement-pca-subscriber-agent.html) section, the ```Practitioner``` resource excludes any *Identifiers* that cannot be disclosed to the subscriber.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Practitioner/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Practitioner``` resource returned.

     **Response Body**:
     * Success: ```Practitioner``` resource that conforms to the [PCA Practitioner](StructureDefinition-pca-practitioner.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  The resource was found and returned.
     * Code 404:  The resource was not found.      "/>
          </interaction>
          <versioning value="versioned"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
        </resource>
        <resource>
          <type value="Provenance"/>
          <profile
                   value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-provenance"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Provenance](StructureDefinition-pca-provenance.html) profile of the ```Provenance``` resource type.

     Each ```Provenance``` resource conforming to the [PCA Provenance](StructureDefinition-pca-provenance.html) profile represents an activity performed by the PCA service (conditionally on behalf of a participating organisation when the target element references a PCA Organization resource) whereby specific data elements of a PCA Organization or PCA Practitioner resource have been initially retrieved, updated or verified from an external system of record.   "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```Provenance``` resource.

     **Behaviour**:

     This operation retrieves an identified ```Provenance``` resource that conforms to the [PCA Provenance](StructureDefinition-pca-practitioner-role.html) profile.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Provenance/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: ```Provenance``` resource that conforms to the [PCA Provenance](StructureDefinition-pca-provenance.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

      The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  The resource was found and returned.
     * Code 404:  The resource was not found.      "/>
          </interaction>
          <versioning value="no-version"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
        </resource>
        <resource>
          <type value="Contract"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Publication Authorisation Record](StructureDefinition-pca-publication-authorisation-record.html) profile and the [PCA Information Use Statement](StructureDefinition-pca-information-use-statement.html) profile of the ```Contract``` resource type.

     A ```Contract``` resource conforming to the [PCA Publication Authorisation Record](StructureDefinition-pca-publication-authorisation-record.html) profile records a decision regarding the publication of a specific service offering (either a ```HealthcareService``` or a ```PractitionerRole```) to a specific partner service. The decision is either to authorise publication or to revoke a previous authority to publish.

     A ```Contract``` resource conforming to the [PCA Information Use Statement](StructureDefinition-pca-information-use-statement.html) profile represents a policy statement by a subscriber organisation's partner service that describes how they will use the information from publisher organisations that is disclosed to the partner service.         "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```Contract``` resource.

     This operation is used to retrieve an identified ```Contract``` resource that conforms to one of the following profiles:
     * [PCA Publication Authorisation Record](StructureDefinition-pca-publication-authorisation-record.html)
     * [PCA Information Use Statement](StructureDefinition-pca-information-use-statement.html)

     Different authorisation rules apply depending on the profile of the ```Contract``` resource being retrieved; see the 'Required OAuth 2.0 scopes' section

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Contract/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: ```Contract``` resource that conforms to the [PCA Publication Authorisation Record](StructureDefinition-pca-publication-authorisation-record.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  The resource was found and returned.
     * Code 404:  The resource was not found.      "/>
          </interaction>
          <interaction>
            <code value="search-type"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **search** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#search)) for ```Contract``` resources.

     **Behaviour**:

     This operation is used to find ```Contract``` resources that conform to the [PCA Information Use Statement](StructureDefinition-pca-information-use-statement.html) profile and that match the search parameters.

     Note that all [PCA Information Use Statement](StructureDefinition-pca-information-use-statement.html) resources in the PCA service are accessible to all authorised client systems.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Contract/{?[parameters]}```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: Bundle containing zero to many ```Contract``` resources that conform to the profile [PCA Information Use Statement](StructureDefinition-pca-information-use-statement.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  Search successfully performed (but may return zero matching results).
     * Code 403:  Server refused to perform the search.      "/>
          </interaction>
          <versioning value="versioned"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
          <searchParam>
            <name value="_profile"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/Resource-profile"/>
            <type value="uri"/>
          </searchParam>
          <searchParam>
            <name value="subject"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/Contract-subject"/>
            <type value="reference"/>
          </searchParam>
          <searchParam>
            <name value="version"/>
            <type value="string"/>
          </searchParam>
        </resource>
        <resource>
          <type value="Task"/>
          <supportedProfile
                            value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-match-record"/>
          <supportedProfile
                            value="http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-partner-service-task"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile of the ```Task``` resource type.

     A ```Task``` resource conforming to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile indicates the matching status of a service offering to a partner service’s local data store.

     A ```Task``` resource conforming to the [PCA Partner Service  Task](StructureDefinition-pca-partner-service-task.html) profile indicates a task created by a partner service via their authorised subscribing system.      "/>
          <interaction>
            <code value="read"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **read** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#read)) of a ```Task``` resource.

     **Behaviour**:

     This operation retrieves an identified ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service](StructureDefinition-pca-partner-service-task.html) profile of the Task resource type.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Task/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain one of the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```
     * ``` Organization/[id]:SS_TaskManager```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.
     The ```SS_Updater``` role **SHALL** be used for reading ```Task```resources conforming to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.
     The ```SS_TaskManager``` role **SHALL** be used for reading ```Task```resources conforming to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.

     **Response Codes**:
     * Code 200:  The resource was found and returned.
     * Code 404:  The resource was not found.      "/>
          </interaction>
          <interaction>
            <code value="create"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **create** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#create)) of a ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.

     **Behaviour**:

     If any of the applicable data validation rules are violated in the input resource then the request is rejected and the error code 422 is returned.

     _Common validation rules:_

     * The resource **SHALL** conform to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the or the [PCA Partner Service](StructureDefinition-pca-partner-service-task.html) profile.
     * *id* **SHALL NOT** be present.
     * *meta.versionId* **SHALL NOT** be present.
     * *meta.lastUpdated* **SHALL NOT** be present.
     * *focus* **SHALL** reference a resource that has been published to one or more [Partner Services](StructureDefinition-pca-partner-service.html) associated with the target PCA Subscriber Agent.

     _PCA Match Record validation rules:_

     * If the resource conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile:
         * *note.text* **SHALL** be a maximum of 200 characters.
         * *owner* **SHALL** reference a [Partner Service](StructureDefinition-pca-partner-service.html) associated with the target PCA Subscriber Agent.

     _PCA Partner Service Task validation rules:_

     * If the resource conforms to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile:
         * *for* **SHALL** reference a [Partner Service](StructureDefinition-pca-partner-service.html) associated with the target PCA Subscriber Agent.

     * If the resource conforms to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile and the ```type``` is 'PartnerServiceCompleteOnlineForm':
         *  *focus* **SHALL** reference either a [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) or [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) resource.
         *  The resource **SHALL** contain *input* elements for each of the following task parameters:
             *  ```type``` = 'dueOn', ```value``` = valueDateTime
             *  ```type``` = 'reason', ```value``` = valueString
             *  ```type``` = 'urlId', ```value``` = valueString
             *  ```type``` = 'formName', ```value``` = valueString
         *  The 'urlId' task paramater ***SHALL*** match one of the partner service website records (configured in PCA) of the [Partner Service](StructureDefinition-pca-partner-service.html) identified by *owner*.
         *  The partner service website record identified by the 'urlId' task paramater ***SHALL*** have a context of use (e.g. Healthcare Service context or Practitioner Role context) that aligns with the resource type referenced in the *focus* element.

     -----

     * If the resource conforms to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile and the ```type``` is 'PartnerServiceProvideMissingInformation':
         *  The resource **SHALL** contain an *input* element for the following task parameter:
             *  ```type``` = 'missingDetails', ```value``` = valueString
         *  If *focus* references a [PCA Organization](StructureDefinition-pca-organization.html) resource, the 'missingDetails' task parameter **SHALL** contain a comma-separated string containing one or more of the following property names:
             *  Fax
             *  Website
             *  PostalAddress
         *  If *focus* references a [PCA Location](StructureDefinition-pca-location.html) resource, the 'missingDetails' task parameter **SHALL** contain a comma-separated string containing one or more of the following property names:
             *  Phone
             *  Email
             *  Fax
             *  Website
             *  PostalAddress
         *  If *focus* references a [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) resource, the 'missingDetails' task parameter **SHALL** contain a comma-separated string containing one or more of the following property names:
             *  Phone
             *  Email
             *  Fax
             *  AfterHoursPhone
             *  Website
             *  PostalAddress
         *  If *focus* references a [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) resource, the 'missingDetails' task parameter **SHALL** contain a comma-separated string containing one or more of the following property names:
             *  PreferredNameAtLocation
             *  NumberOfDays
             *  HpiiIdentifier
             *  MedicareProviderNumber

     -----

     * If the resource conforms to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile and the ```type``` is 'PartnerServiceVerifyInformation':
         *  The resource **SHALL** contain one *input* element for the following task parameter:
             *  ```type``` = 'verifyDetails', ```value``` = valueString
         *  The *input* element **SHALL** use the [PCA Property Name](StructureDefinition-pca-property-name.html) extension to identify the property name:
             *  If *focus* references a [PCA Organization](StructureDefinition-pca-organization.html) resource, the extension **SHALL** use one of the following property names:
                 *  Fax
                 *  Website
             *  If *focus* references a [PCA Location](StructureDefinition-pca-location.html) resource, the extension **SHALL** use one of the following property      names:
                 *  Phone
                 *  Email
                 *  Fax
                 *  Website
             *  If *focus* references a [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) resource, the extension **SHALL** use one of the following property names:
                 *  Phone
                 *  Email
                 *  Fax
                 *  AfterHoursPhone
                 *  Website
             *  If *focus* references a [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) resource, the extension **SHALL** use one of the following property names:
                 *  PreferredNameAtLocation
                 *  NumberOfDays
         *  The *input* element **SHALL** use valueString to record a new suggested value of the property, if the Partner Service chooses to suggest a new value.

     **HTTP interaction signature**:
     * ```POST [subscriber agent base url]/Task```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the new ```Task``` resource.

     **Response Body**:
     * Success: ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.
    *  Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```
     * ``` Organization/[id]:SS_TaskManager```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.
     The ```SS_Updater``` role **SHALL** be used for creating ```Task``` resources conforming to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.
     The ```SS_TaskManager``` role **SHALL** be used for creating ```Task``` resources conforming to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.

     **Response Codes**:
     * Code 201:  The resource was successfully created.
     * Code 400:  The input resource could not be parsed or failed basic FHIR validation rules.
     * Code 404:  The resource type is not supported, or not a FHIR end-point.
     * Code 422:  The input resource violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <interaction>
            <code value="update"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **update** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#update)) of a ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.

     **Behaviour**:

     If the 'if-match' HTTP header is not provided in the request, then the PCA Subscriber Agent will reject the request and return the error code 400.

     If the 'if-match' HTTP header does not match the current version, then the PCA Subscriber Agent will reject the request and return the error code 412.

     If any of the applicable data validation rules are violated in the input resource then the request is rejected and the error code 422 is returned.

     _Common validation rules:_

     * The resource **SHALL** conform to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.
     * *id* **SHALL** be identical to the corresponding value in the version of the ```Task``` identified in the 'if-match' HTTP header.
     * *meta.versionId* **SHALL NOT** be present.
     * *meta.lastUpdated* **SHALL NOT** be present.

     _PCA Match Record validation rules:_

     * If the resource conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile:
         * *owner* **SHALL** reference a [Partner Service](StructureDefinition-pca-partner-service.html) associated with the target PCA Subscriber Agent.
         * Only changes to *status* (and optionally *note.text*) will be accepted; changes to any other element values will not be accepted when updating an existing ```Task```.
         * *note.text* **SHALL** only be updated if *status* is being changed from 'completed' to 'failed'.
         * *note.text* **SHALL** be a maximum of 200 characters.

     _PCA Partner Service Task validation rules:_

     * If the resource conforms to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile:
         * *for* **SHALL** reference a [Partner Service](StructureDefinition-pca-partner-service.html) associated with the target PCA Subscriber Agent.
         * *type* **SHALL** be 'PartnerServiceCompleteOnlineForm'.
         * Only a change to *status* from 'requested' to 'completed' will be accepted; changes to any other element values will not be accepted when updating an existing ```Task```.

     **HTTP interaction signature**:
     * ```PUT [subscriber agent base url]/Task/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```
     * ```if-match [version id]``` where [version id] is the version of the ```Task``` being updated.

     **Request Body**:
     ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Task``` resource returned.

     **Response Body**:
     * Success: ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.
    *  Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```
     * ``` Organization/[id]:SS_TaskManager```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.
     The ```SS_Updater``` role **SHALL** be used for updating ```Task``` resources conforming to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.
     The ```SS_TaskManager``` role **SHALL** be used for updating ```Task``` resources conforming to the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.

     **Response Codes**:
     * Code 200:  The resource was found and returned.
     * Code 400:  Client error:  request did not include the *if-match* HTTP header.
     * Code 404:  The resource was not found.
     * Code 412:  The version id given in the *if-Match* HTTP request header does not match the current version.
     * Code 422:  The input resource violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <interaction>
            <code value="patch"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **patch** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#patch)) of a ```Task``` resource.

     **Behaviour**:

     This operation is used to update an identified ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile via a JSON or XML patch document. This operation will only process a patch operation for adding or updating an *identifier* element.

     If any of the following data validation rules are violated, then the request is rejected and the error code 422 is returned:

     * The patch document **SHALL** only contain an operation for adding or updating an *identifier* element.
     * Only one *identifier* element per *identifier.system* **SHALL** be allowed for the identified ```Task``` resource.
     * The patch operation **SHALL** only add or update an *identifier* element where *identifier.system* identifies a subscriber identifier system that is owned by the participating organisation associated with the target PCA Subscriber Agent.
     * The patch operation **SHALL** only add or update an *identifier* element where a [PCA Match Record](StructureDefinition-pca-match-record.html) exists within the PCA service with:
       * A *status* of 'completed', and;
       * A *focus* referencing the ```Task``` resource, and;
       * An *owner* referencing a [PCA Partner Service](StructureDefinition-pca-partner-service.html) of the participating organisation associated with the target PCA Subscriber Agent.

     **HTTP interaction signature**:
     * ```PATCH [subscriber agent base url]/Task/[id]```

     **Mandatory Request Headers**:
     * ```Accept: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Content-Type: application/json-patch+json;charset=utf-8``` or ```Accept: application/xml-patch+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * A JSON Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc6902](https://datatracker.ietf.org/doc/html/rfc6902) with a content type of ```application/json-patch+json```, or;
     * An XML Patch document that conforms to [https://datatracker.ietf.org/doc/html/rfc5261](https://datatracker.ietf.org/doc/html/rfc5261) with a content type of ```application/xml-patch+xml```

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```ETag: [version id]``` where [version id] identifies the version of the ```Task``` resource returned.

     **Response Body**:
     * Success: ```Task``` resource that conforms to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Updater```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     *  Code 200:  The resource was found and returned.
     *  Code 404:  The resource was not found.
     *  Code 422:  The input patch document violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <interaction>
            <code value="search-type"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **search** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#search)) for ```Task``` resources that conform to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.

     **Behaviour**:

     The operation is used to find ```Task``` resources that that conform to the profile [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile and that match the search parameters.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/Task/{?[parameters]}```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: Bundle that contains zero to many ```Task``` resources that conform to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile or the [PCA Partner Service Task](StructureDefinition-pca-partner-service-task.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  Search successfully performed (but may return zero matching results).
     * Code 403:  Server refused to perform the search.      "/>
          </interaction>
          <versioning value="versioned-update"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
          <searchParam>
            <name value="_profile"/>
            <definition
                        value="http://hl7.org/fhir/SearchParameter/Resource-profile"/>
            <type value="uri"/>
          </searchParam>
          <searchParam>
            <name value="subject"/>
            <definition value="http://hl7.org/fhir/SearchParameter/Task-subject"/>
            <type value="reference"/>
          </searchParam>
          <searchParam>
            <name value="owner"/>
            <definition value="http://hl7.org/fhir/SearchParameter/Task-owner"/>
            <type value="reference"/>
          </searchParam>
        </resource>
        <resource>
          <type value="Subscription"/>
          <profile value="http://hl7.org/fhir/StructureDefinition/Subscription"/>
          <documentation
                         value="

     This section defines the supported interactions for the [PCA Subscription](StructureDefinition-pca-subscription.html) profile of the ```Subscription``` resource type.

     The [PCA Subscription](StructureDefinition-pca-subscription.html) profile of ```Subscription``` is used by subscribing systems to register for notifications from the PCA service when new or updated service offerings are available, or when publication of existing service offerings has been newly revoked.       "/>
          <interaction>
            <code value="create"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **create** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#create)) of a ```Subscription``` resource conforming to the [PCA Subscription](StructureDefinition-pca-subscription.html) profile.

     **Behaviour**:

     This operation is used to register a callback to receive a notification whenever there are changes in the data set that is published to a subscriber.

     A notification is simply a HTTP POST without any content – the purpose is to trigger the subscriber’s client system to get the available service offerings by invoking the [whole system search operation](CapabilityStatement-pca-subscriber-agent.html#search-system).

     If any of the following data validation rules are violated in the input resource, then the request is rejected and the error code 422 is returned:
     * *status* **SHALL** be 'requested'
     * *reason* **SHALL** be 'subscriber change notifications'
     * *criteria*  **SHALL** be a space separated list of resource types from the list 'HealthcareService', 'PractitionerRole', 'Location', 'Organization', 'Practitioner', 'Provenance', 'Contract', 'Task'
     * *channel.type*  **SHALL** be 'rest-hook'
     * *channel.endpoint* **SHALL** be the URL of an endpoint that is operated by (or on behalf of) the subscriber for receiving notifications. The protocol **SHALL** be https.
     * *channel.payload* **SHALL NOT** be present – its absence indicates that the subscriber will not receive any resources via this endpoint.
     * *channel.header* **SHALL** be set to 'Authorization: Bearer [secret string]' where [secret string] is the basic authentication string, set by the subscriber organisation, that is used to authenticate the PCA Subscriber Agent to the notification receiving endpoint.

     **HTTP interaction signature**:
     * ```POST [subscriber agent base url]/Subscription```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * ```Subscription``` resource that conforms to the [PCA Subscription](StructureDefinition-pca-subscription.html) profile.

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: ```Subcription``` resource that conforms to the [PCA Subscription](StructureDefinition-pca-subscription.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 201:  The resource was successfully created.
     * Code 400:  The input resource could not be parsed or failed basic FHIR validation rules.
     * Code 404:  The resource type is not supported, or not a FHIR end-point.
     * Code 422:  The input resource violated applicable FHIR profiles or server data validation rules.      "/>
          </interaction>
          <interaction>
            <code value="search-type"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **search** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#search)) for a ```Subscription``` resource that is associated with the target Subscriber Agent and that conforms to the [PCA Subscription](StructureDefinition-pca-subscription.html) profile.

     **Behaviour**:

     This operation is used to find a ```Subscription``` resource that is associated with the target Subscriber Agent and that conforms to the [PCA Subscription](StructureDefinition-pca-subscription.html) profile.

     **HTTP interaction signature**:

     * ```GET [subscriber agent base url]/Subscription/```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: ```Bundle``` that contains zero or one ```Subscription``` resource that that is associated with the target Subscriber Agent and that conforms to the [PCA Subscription](StructureDefinition-pca-subscription.html) profile.
     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  Search successfully performed (but may return zero matching results).
     * Code 403:  Server refused to perform the search.       "/>
          </interaction>
          <interaction>
            <code value="delete"/>
            <documentation
                           value="**Definition**:

     This operation is a RESTful **delete** interaction (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#delete)) of a ```Subscription``` resource.

     **Behaviour**:

     This operation is used to deregister an existing notification callback.

     **HTTP interaction signature**:
     * ```DELETE [subscriber agent base url]/Subscription/[id]```

     **Mandatory Request Headers**:
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * (No request body)

     **Response Body**:
     * (No request body)

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 202:  The deletion was accepted.
     * Code 404:  The resource was not found.      "/>
          </interaction>
          <versioning value="no-version"/>
          <readHistory value="false"/>
          <updateCreate value="false"/>
          <conditionalCreate value="false"/>
          <conditionalRead value="not-supported"/>
          <conditionalUpdate value="false"/>
          <conditionalDelete value="not-supported"/>
        </resource>
        <interaction>
          <code value="search-system"/>
          <documentation
                         value="**Definition**:
     This operation is a RESTful *search* interaction (whole system interaction), across multiple resource types (as described in the [FHIR specification](https://www.hl7.org/fhir/http.html#search)).

     **Behaviour**:
     This operation is used by a client system operated by a subscriber organisation to get resources that match the specified search parameters and that have been published to the subscriber organisation's partner services.

     The following  search parameters are supported:

     * *_lastUpdated* is used to get the resources that have been added or changed since the requesting system last synchronised their local data store with PCA Subscriber Agent.  This search parameter supports the ```gt``` and ```lt``` comparison prefixes.
     * *_type* is used to filter the resources returned by their resource type. The available types are:

       * ```HealthcareService``` (returns resources conforming to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile)
       * ```PractitionerRole``` (returns resources conforming to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile)
       * ```Organization``` (returns resources conforming to the [PCA Organization](StructureDefinition-pca-organization.html) profile)
       * ```Location``` (returns resources conforming to the [PCA Location](StructureDefinition-pca-location.html) profile)
       * ```Practitioner``` (returns resources conforming to the [PCA Practitioner](StructureDefinition-pca-practitioner.html) profile)
       * ```Provenance``` (returns resources conforming to the [PCA Provenance](StructureDefinition-pca-provenance.html) profile)
       * ```Contract``` (returns resources conforming to the [PCA Publication Authorisation Record](StructureDefinition-pca-publication-authorisation-record.html) profile)
       * ```Task``` (returns resources conforming to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile)

         * Note: a ```Contract``` resource with 'status' of 'revoked' indiates that a service offering that was previously published to a partner service is no longer available to that partner service. In this case the ```Contract``` resource will reference a *target* ```Organization```, ```Location```, ```HealthcareService```, or ```PractitionerRole``` that is not included in the ```Bundle``` (but its *id* will identify the resource which is no longer published to the subscriber).

     * *_include* (and *_include:iterate*) are used in order that all the resources that match the *_lastUpdated* and *_type* filters will be accompanied, in the result ```Bundle```, with all the other resources which they reference (directly or indirectly).  Note that the use of *_include* (and *_include:iterate*) means that a resource may be present in the result ```Bundle``` either because it matched the other query parameters or because it was referenced (possibly indirectly) by another resource that matched the other query parameters.
     * *_filter* is used to only get the resources that have been published to a specific [PCA Partner Service](StructureDefinition-pca-partner-service.html) of the subscriber organisation.  If the *_filter* parameter is not present, the operation will return resources that have been published to all of the subscriber organisation's partner services.  The *_filter* parameter supports the following query expression:

       * ```HealthcareService: id eq [FHIR ID of partner service]```

     All of the following query parameters are required in order to receive the complete set of resources that have been created, changed or published to all the subscriber organisation's partner services since *[last_synchronized]*:

     ``` _lastUpdated=[last_synchronized] ```
     ```_type=HealthcareService,PractitionerRole,Practitioner,Organization,Location,Provenance,Contract,Task ```
     ```_include=Location:organization ```
     ```_include=HealthcareService:organization ```
     ```_include=HealthcareService:location ```
     ```_include=PractitionerRole:organization ```
     ```_include=PractitionerRole:location ```
     ```_include=PractitionerRole:service ```
     ```_include=PractitionerRole:practitioner ```
     ```_include=Provenance:target ```
     ```_include=Contract:subject ```
     ```_include:iterate=HealthcareService:organization  ```
     ```_include:iterate=HealthcareService:location ```
     ```_include:iterate=PractitionerRole:organization ```
     ```_include:iterate=PractitionerRole:location ```
     ```_include:iterate=PractitionerRole:service ```
     ```_include:iterate=PractitionerRole:practitioner ```

     As described [above](CapabilityStatement-pca-subscriber-agent.html) the resources returned in the Bundle exclude any *Identifiers* (e.g. HPI-Is) that cannot be disclosed to the subscriber.

     This operation supports 'paging' ([see FHIR specification](https://www.hl7.org/fhir/search.html#Paging)).  If there are too many resources to return in one ```Bundle```, the FHIR server adds a *next* link to the response ```Bundle```. The contents of the result ```Bundle``` therefore comprise all instances of the requested resource types whose *lastUpdated* timestamp is greater than the &lt;lastSync&gt; in the request query expression and less than or equal to &lt;lastInBundle&gt; where &lt;lastInBundle&gt; is the greatest *lastUpdated* value of all resources included in the result ```Bundle```. The Subscriber Agent FHIR server sets the *next* link to the filter expression that was used in the original request except that &lt;lastSync&gt; is replaced with &lt;lastInBundle&gt;. If the *next* link is not present in the Bundle, then there are no more service offerings available.

     **HTTP interaction signature**:
     * ```GET [subscriber agent base url]/?[parameters]```

     **Mandatory Request Headers**:
     * ```Accept: application/fhir+json;charset=utf-8``` or ```Accept: application/fhir+xml;charset=utf-8```
     * ```Authorization: Bearer [token]```

     **Request Body**:
     * (No request body)

     **Mandatory Response Headers**:
     * ```Content-Type: application/fhir+json;charset=utf-8``` or ```Content-Type: application/fhir+xml;charset=utf-8```

     **Response Body**:
     * Success: ```Bundle``` that contains zero to many resources (where the resource type was included in the filter expression of the search request) that conform to the following [PCA profiles](profiles.html):

       * ```HealthcareService``` resources conforming to the [PCA Healthcare Service](StructureDefinition-pca-healthcare-service.html) profile
       * ```PractitionerRole``` resources conforming to the [PCA Practitioner Role](StructureDefinition-pca-practitioner-role.html) profile
       * ```Organization``` resources conforming to the [PCA Organization](StructureDefinition-pca-organization.html) profile
       * ```Location``` resources conforming to the [PCA Location](StructureDefinition-pca-location.html) profile
       * ```Practitioner``` resources conforming to the [PCA Practitioner](StructureDefinition-pca-practitioner.html) profile
       * ```Provenance``` resources conforming to the [PCA Provenance](StructureDefinition-pca-provenance.html) profile
       * ```Contract``` resources conforming to the [PCA Publication Authorisation Record](StructureDefinition-pca-publication-authorisation-record.html) profile

         * ```Contract``` resources will be returned that reference each of the ```HealthcareService``` or ```PractitionerRole``` resources that are included in the ```Bundle``` - these ```Contract``` resources have a *status* of “executed” if the associated PCA Partner Service is active, or a *status* of “cancelled” if the associated PCA Partner Service is inactive).
         * ```Contract``` resources will also be returned that reference ```HealthcareService``` or ```PractitionerRole``` resources that are not in the ```Bundle``` but for which authority to publish has been revoked - these ```Contract``` resources will have a *status* of “revoked”).

       * ```Task``` resources conforming to the [PCA Match Record](StructureDefinition-pca-match-record.html) profile

     * Error: ```OperationOutcome``` resource (see [FHIR specification](https://www.hl7.org/fhir/operationoutcome.html)).

     **Required OAuth 2.0 scopes**:

     The *scope* string **SHALL** contain the following *scoped role*:
     * ``` Organization/[id]:SS_Receiver```

     Where [id] **SHALL** identify the ```Organization``` associated with the target PCA Subscriber Agent.

     **Response Codes**:
     * Code 200:  Search successfully performed (but may return zero matching results).
     * Code 400:  The input query could not be parsed, or the [PCA Partner Service](StructureDefinition-pca-partner-service.html) referenced in the ```_filter``` parameter could not be found or is inactive.
     * Code 403:  Server refused to perform the search.     "/>
        </interaction>
        <searchParam>
          <name value="_lastUpdated"/>
          <definition
                      value="http://hl7.org/fhir/SearchParameter/Resource-lastUpdated"/>
          <type value="date"/>
        </searchParam>
        <searchParam>
          <name value="_type"/>
          <type value="token"/>
        </searchParam>
        <searchParam>
          <name value="_include"/>
          <type value="special"/>
        </searchParam>
        <searchParam>
          <name value="_include:iterate"/>
          <type value="special"/>
        </searchParam>
        <searchParam>
          <name value="_filter"/>
          <type value="special"/>
        </searchParam>
        <searchParam>
          <name value="_page"/>
          <type value="special"/>
        </searchParam>
        <searchParam>
          <name value="_count"/>
          <type value="special"/>
        </searchParam>
        <searchParam>
          <name value="_resultId"/>
          <type value="special"/>
        </searchParam>
      </rest>
    </CapabilityStatement>