Generated Narrative: CapabilityStatement GPCCMPServerCapabilityStatement GPCCMP Server Capability Statement Implementation Guide Version: 0.1.0 FHIR Version: 4.0.1 Supported Formats: SHALL support json Published on: 2025-12-22 Published by: AEHRC CSIRO Note to Implementers: FHIR Capabilities 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. FHIR RESTful Capabilities Mode: server GPCCMP Launch Server SHALL: Support the AU Core AllergyIntolerance resource profile Support the AU Core Condition resource profile Support the AU Core Encounter resource profile Support the AU Core Medication profile Support the AU Core MedicationStatement profile Support the AU Core Patient resource profile Support the AU Core Practitioner resource profile Support the AU Core PractitionerRole resource profile Support the SDC Standard Questionnaire Response resource profile Implement the RESTful behavior according to the FHIR specification Support JSON source formats for all interactions Security Enable CORS: yes Security services supported: SMART-on-FHIR GPCCMP Launch Server MAY: Support CORS headers Support SMART on FHIR security services Also see the AU Core Security and Privacy section for general considerations and recommendations. Summary of System-wide Interactions SHALL support the transactioninteraction described as follows: The server SHALL support the transaction interaction for all resources. Capabilities by Resource/Profile Summary The summary table lists the resources that are part of this configuration, and for each resource it lists: The relevant profiles (if any) The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them. The required, recommended, and some optional search parameters (if any). The linked resources enabled for _include The other resources enabled for _revinclude The operations on the resource (if any) Resource Type Profile R S U C Searches _include _revinclude Operations AllergyIntolerance Supported Profiles AU Core AllergyIntolerance Y patient Condition Supported Profiles AU Core Condition Y patient, category, patient+category Encounter Supported Profiles AU Core Encounter Y Medication Supported Profiles AU Core Medication Y MedicationStatement Supported Profiles AU Core MedicationStatement Y patient, status, _include, patient+status, patient+status+_include MedicationStatement:medication Patient Supported Profiles AU Core Patient Y Practitioner Supported Profiles AU Core Practitioner Y QuestionnaireResponse Supported Profiles SDC Standard Questionnaire Response Y Y Y Y patient, questionnaire, status, _count, _sort, patient+_count+_sort, patient+_count+_sort+questionnaire, patient+_count+_sort+status Resource Conformance: SHALL AllergyIntolerance Core FHIR Resource AllergyIntolerance Reference Policy Interaction summary SHALL support search-type. Supported Profiles AU Core AllergyIntolerance Documentation The server SHALL support the AllergyIntolerance resource, the AU Core profile and the conformance expectations for the AllergyIntolerance resource. Search Parameters Conformance Parameter Type Documentation SHALL patient reference The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. Resource Conformance: SHALL Condition Core FHIR Resource Condition Reference Policy Interaction summary SHALL support search-type. Supported Profiles AU Core Condition Documentation The server SHALL support the Condition resource, the AU Core profile and the conformance expectations for the Condition resource. Search Parameters Conformance Parameter Type Documentation MAY patient reference The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. MAY category token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both. Combined Search Parameters Conformance Parameters Types SHALL patient+category reference+token Resource Conformance: MAY Encounter Core FHIR Resource Encounter Reference Policy Interaction summary SHALL support read. Supported Profiles AU Core Encounter Documentation The server MAY support the Encounter resource. If it does, it SHALL support the AU Core profile and the conformance expectations for the Encounter resource. Resource Conformance: MAY Medication Core FHIR Resource Medication Reference Policy Interaction summary SHALL support read. Supported Profiles AU Core Medication Documentation If an external reference to a Medication resource is used in MedicationStatement, then the server SHALL support the Medication resource, the AU Core profile and the conformance expectations for the Medication resource. Resource Conformance: SHALL MedicationStatement Core FHIR Resource MedicationStatement Reference Policy Interaction summary SHALL support search-type. Supported Profiles AU Core MedicationStatement Documentation The server SHALL support the MedicationStatement resource, the AU Core profile and the conformance expectations for the MedicationStatement resource. If a medication in a MedicationStatement resource is represented as an external Medication resource reference, the server SHALL support the _include parameter for searching this element (MedicationStatement:medication) Search Parameters Conformance Parameter Type Documentation MAY patient reference The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. MAY status token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both. The client SHALL support multipleOr. The server SHALL support multipleOr. MAY _include reference If a medication in a MedicationStatement resource is represented as an external Medication resource reference, the server SHALL support the _include parameter for searching this element (MedicationStatement:medication). The client SHALL support this method. Combined Search Parameters Conformance Parameters Types SHALL patient+status reference+token MAY patient+status+_include reference+token+reference Resource Conformance: SHALL Patient Core FHIR Resource Patient Reference Policy Interaction summary SHALL support read. Supported Profiles AU Core Patient Documentation The server SHALL support the Patient resource, AU Core profile and the conformance expectations for the Patient resource. Resource Conformance: SHALL Practitioner Core FHIR Resource Practitioner Reference Policy Interaction summary SHALL support read. Supported Profiles AU Core Practitioner Documentation The server SHALL support the Practitioner resource, AU Core profile and the conformance expectations for the Practitioner resource. Resource Conformance: SHALL QuestionnaireResponse Core FHIR Resource QuestionnaireResponse Reference Policy Interaction summary SHALL support read, search-type, create, update. Supported Profiles SDC Standard Questionnaire Response Documentation The server SHALL support the QuestionnaireResponse resource, SDC profile and the conformance expectations for the QuestionnaireResponse resource. Search Parameters Conformance Parameter Type Documentation MAY patient reference The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. MAY questionnaire reference The client SHALL provide at least a id value and MAY provide both the Type and id values. The server SHALL support both. The client and server SHALL support chained search questionnaire.title using the :contains modifier. MAY status token The client SHALL provide at least a code value and MAY provide both the code and system values. The server SHALL support both. MAY _count number The client and server SHALL support search result limiting. MAY _sort string The client and server SHALL support search result sorting by authored and MAY support other values. Combined Search Parameters Conformance Parameters Types SHALL patient+_count+_sort reference+number+string SHALL patient+_count+_sort+questionnaire reference+number+string+reference SHALL patient+_count+_sort+status reference+number+string+token
This CapabilityStatement describes the expected capabilities for systems to exchange the data needed to support the [GP Chronic Condition Management Plan](Questionnaire-GPChronicConditionManagementPlan.html). It lists the server's conformance expectations for the resource types required as Questionnaire launch context, resource types required to support prepopulation of the form and QuestionnaireResponse requirements for managing form responses. These expectations include supported FHIR profiles, RESTful operations, and search parameters.
GPCCMP Launch Server **SHALL**: 1. Support the [AU Core AllergyIntolerance resource profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-allergyintolerance.html) 1. Support the [AU Core Condition resource profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-condition.html) 1. Support the [AU Core Encounter resource profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-encounter.html) 1. Support the [AU Core Medication profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-medication.html) 1. Support the [AU Core MedicationStatement profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-medicationstatement.html) 1. Support the [AU Core Patient resource profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-patient.html) 1. Support the [AU Core Practitioner resource profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-practitioner.html) 1. Support the [AU Core PractitionerRole resource profile](https://hl7.org.au/fhir/core/2.0.0-preview/StructureDefinition-au-core-practitionerrole.html) 1. Support the [SDC Standard Questionnaire Response resource profile](https://build.fhir.org/ig/HL7/sdc/en/StructureDefinition-sdc-questionnaireresponse.html) 1. Implement the RESTful behavior according to the FHIR specification 1. Support JSON source formats for all interactions
GPCCMP Launch Server **MAY**: 1. Support CORS headers 1. Support SMART on FHIR security services Also see the [AU Core Security and Privacy](https://hl7.org.au/fhir/core/2.0.0-preview/security.html) section for general considerations and recommendations.
The server **SHALL** support the AllergyIntolerance resource, the AU Core profile and the conformance expectations for the AllergyIntolerance resource.
The client **SHALL** provide at least a id value and **MAY** provide both the Type and id values. The server **SHALL** support both.
The server **SHALL** support the Condition resource, the AU Core profile and the conformance expectations for the Condition resource.
The client **SHALL** provide at least a code value and **MAY** provide both the system and code values. The server **SHALL** support both.
The server **MAY** support the Encounter resource. If it does, it **SHALL** support the AU Core profile and the conformance expectations for the Encounter resource.
If an external reference to a Medication resource is used in MedicationStatement, then the server **SHALL** support the Medication resource, the AU Core profile and the conformance expectations for the Medication resource.
The server **SHALL** support the MedicationStatement resource, the AU Core profile and the conformance expectations for the MedicationStatement resource. If a medication in a MedicationStatement resource is represented as an external Medication resource reference, the server **SHALL** support the `_include` parameter for searching this element (`MedicationStatement:medication`)
The client **SHALL** provide at least a code value and **MAY** provide both the system and code values. The server **SHALL** support both. The client **SHALL** support `multipleOr`. The server **SHALL** support `multipleOr`.
If a medication in a MedicationStatement resource is represented as an external Medication resource reference, the server **SHALL** support the `_include` parameter for searching this element (`MedicationStatement:medication`). The client **SHALL** support this method.
The server **SHALL** support the Patient resource, AU Core profile and the conformance expectations for the Patient resource.
The server **SHALL** support the Practitioner resource, AU Core profile and the conformance expectations for the Practitioner resource.
The server **SHALL** support the QuestionnaireResponse resource, SDC profile and the conformance expectations for the QuestionnaireResponse resource.
The client **SHALL** provide at least a id value and **MAY** provide both the Type and id values. The server **SHALL** support both. The client and server **SHALL** support chained search questionnaire.title using the :contains modifier.
The client **SHALL** provide at least a code value and **MAY** provide both the code and system values. The server **SHALL** support both.
The client and server **SHALL** support search result limiting.
The client and server **SHALL** support search result sorting by authored and **MAY** support other values.
The server **SHALL** support the transaction interaction for all resources.