GP Chronic Condition Management Plan
0.1.0 - ci-build
GP Chronic Condition Management Plan, published by AEHRC CSIRO. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/aehrc/gpccmp-fhir-ig/ and changes regularly. See the Directory of published versions
| Official URL: https://gpccmp.csiro.au/ig/CapabilityStatement/GPCCMPClientCapabilityStatement | Version: 0.1.0 | |||
| Draft as of 2025-12-22 | Computable Name: GPCCMPClientCapabilityStatement | |||
This CapabilityStatement describes the expected capabilities for systems to exchange the data needed to support the GP Chronic Condition Management Plan. It lists the client'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.
Raw OpenAPI-Swagger Definition file | Download
jsonNote 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.
serverGPCCMP Launch Server SHALL:
SMART-on-FHIRGPCCMP 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.
transactioninteraction described as follows:The server SHALL support the transaction interaction for all resources.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| 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 |
The server SHALL support the AllergyIntolerance resource, the AU Core profile and the conformance expectations for the AllergyIntolerance resource.
| 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. |
The server SHALL support the Condition resource, the AU Core profile and the conformance expectations for the Condition resource.
| 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. |
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
_includeparameter for searching this element (MedicationStatement:medication)
| 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 The server SHALL support |
| MAY | _include | reference | If a medication in a MedicationStatement resource is represented as an external Medication resource reference, the server SHALL support the 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.
read, search-type, create, update.The server SHALL support the QuestionnaireResponse resource, SDC profile and the conformance expectations for the QuestionnaireResponse resource.
| 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. |
| 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 |