This is the Capability statement for a PCA Subscriber Agent FHIR server.
\nMode | SERVER |
Description | A PCA Subscriber Agent manages the service offerings for one subscriber organisation (also referred to as a 'business partner' in the PCA portal). \nThe 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. \nThe subscriber agent base URL for a particular organisation is available via the PCA portal on the 'Organisation Details' screen of the subscriber organisation. \nA 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. \nPublication process \nA PCA Publisher Agent creates the The authority to publish is represented using Identifier disclosure rules \nThe PCA service enforces certain business rules regarding the disclosure of Identifiers (including subscriber-issued identifiers) in the resources that it makes available to subscribers. \nThe 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. \nIn the case of HPI-Is these identifier disclosure rules ensure that relevant legal requirements are complied with. \nOther identifier disclosure rules are defined by the PCA operator. \nThe identifier disclosure rules are applied automatically at the time that the resource is retrieved by the target PCA Subscriber Agent. \nAuthorisation rules \nAuthorised 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'. \nResource profiles and extensions \nThis 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. \n |
Transaction | |
System History | |
System Search | y |
Resource Type | Profile | Read | Search | Update | Patch | Create | Delete |
---|---|---|---|---|---|---|---|
Organization | http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-organization | y | y | ||||
Location | http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-location | y | y | ||||
HealthcareService | y | y | y | ||||
PractitionerRole | http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner-role | y | y | ||||
Practitioner | http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-practitioner | y | |||||
Provenance | http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-provenance | y | |||||
Contract | y | y | |||||
Task | http://pca.digitalhealth.gov.au/fhir/4.0/StructureDefinition/pca-match-record | y | y | y | |||
Subscription | http://hl7.org/fhir/StructureDefinition/Subscription | y | y | y |