ACP CapabilityStatement Provider

Advance Care Planning (PZP)
1.0.0-rc2 - trial-use

Advance Care Planning (PZP), published by IKNL. This guide is not an authorized publication; it is the continuous build for version 1.0.0-rc2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IKNL/PZP-FHIR-R4/ and changes regularly. See the Directory of published versions

CapabilityStatement: ACP CapabilityStatement Provider

Official URL: https://api.iknl.nl/docs/pzp/r4/CapabilityStatement/ACP-CapabilityStatementProvider				Version: 1.0.0-rc2
Active as of 2026-03-03				Computable Name: ACPCapabilityStatementProvider
Copyright/Legal: Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.

This CapabilityStatement describes the rules for the ACP Actor Provider that is responsible for providing responses to queries submitted by ACP Consultors.

Raw OpenAPI-Swagger Definition file | Download

Implementation Guide Version: 1.0.0-rc2
FHIR Version: 4.0.1
Supported Formats: SHALL support json, SHALL support xml
Published on: 2026-03-03
Published by: IKNL

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`

The ACP Provider SHALL:

Support at least the QuestionnaireResponse resource, or as many of the other resources defined in this CapabilityStatement for which the Provider has information available.
Implement the RESTful behaviour according to the FHIR specification.
Support both JSON and XML formats for all ACP resource interactions.
Declare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.

Security

Accessing ACP information is subject to strict privacy and security rules. All API requests MUST be properly authenticated and authorized. The client application is expected to use a secure mechanism to obtain an access token with the necessary scopes to read the patient's clinical data. The exact methods may be found in the used infrastructure specification and agreements of e.g. LSP, Twiin and or Nuts.

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	Searches	`_include`
Encounter	Supported Profiles ACP Encounterversion: 1.0.0-rc2)	Y	Y	patient, reason-reference	`Encounter:reason-reference`
Procedure	Supported Profiles ACP Procedureversion: 1.0.0-rc2)	Y	Y	patient, code	`Procedure:encounter`
Consent	Supported Profiles ACP AdvanceDirectiveversion: 1.0.0-rc2) ACP TreatmentDirectiveversion: 1.0.0-rc2)	Y	Y	patient, scope, category	`Consent:actor`
Goal	Supported Profiles ACP Medical Policy Goalversion: 1.0.0-rc2)	Y	Y	patient, category
Observation	Supported Profiles ACP Organ Donation Choice Registration in Donor Registerversion: 1.0.0-rc2) ACP Sense of Purposeversion: 1.0.0-rc2) ACP Position Regarding Euthanasiaversion: 1.0.0-rc2) ACP Preferred Place of Deathversion: 1.0.0-rc2) ACP Specific Care Wishesversion: 1.0.0-rc2)	Y	Y	patient, code
DeviceUseStatement	Supported Profiles ACP MedicalDeviceversion: 1.0.0-rc2)	Y	Y	patient, device	`DeviceUseStatement:device`
Device	Supported Profiles ACP MedicalDevice Product ICDversion: 1.0.0-rc2)	Y	Y	type	`DeviceUseStatement:device`
CommunicationRequest	Supported Profiles ACP Request to Inform Relativesversion: 1.0.0-rc2)	Y	Y	patient, category
RelatedPerson	Supported Profiles ACP ContactPersonversion: 1.0.0-rc2)	Y
Practitioner	Supported Profiles ACP HealthProfessional Practitionerversion: 1.0.0-rc2)	Y
PractitionerRole	Supported Profiles ACP HealthProfessional PractitionerRoleversion: 1.0.0-rc2)	Y
Patient	Supported Profiles ACP Patientversion: 1.0.0-rc2)	Y
QuestionnaireResponse		Y	Y	patient, questionnaire

Resource Conformance: SHOULDEncounter

Core FHIR Resource
Encounter

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP Encounterversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	patient	`reference`
SHALL	reason-reference	`reference`	The provider SHOULD support chained search Procedure.code using the SNOMED CT code as defined in the ACP Procedure profile.

Resource Conformance: SHOULDProcedure

Core FHIR Resource
Procedure

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP Procedureversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	patient	`reference`
SHALL	code	`token`

Resource Conformance: SHOULDConsent

Core FHIR Resource
Consent

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP AdvanceDirectiveversion: 1.0.0-rc2)
ACP TreatmentDirectiveversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type
SHALL	patient	`reference`
SHALL	scope	`token`
SHALL	category	`token`

Resource Conformance: SHOULDGoal

Core FHIR Resource
Goal

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP Medical Policy Goalversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	patient	`reference`
SHALL	category	`token`

Resource Conformance: SHOULDObservation

Core FHIR Resource
Observation

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP Organ Donation Choice Registration in Donor Registerversion: 1.0.0-rc2)
ACP Sense of Purposeversion: 1.0.0-rc2)
ACP Position Regarding Euthanasiaversion: 1.0.0-rc2)
ACP Preferred Place of Deathversion: 1.0.0-rc2)
ACP Specific Care Wishesversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	patient	`reference`
SHALL	code	`token`

Resource Conformance: SHOULDDeviceUseStatement

Core FHIR Resource
DeviceUseStatement

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP MedicalDeviceversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	patient	`reference`
SHALL	device	`reference`	The provider SHOULD support chained search Device.type using the codes as defined in the ACP Procedure profile.

Resource Conformance: SHOULDDevice

Core FHIR Resource
Device

Reference Policy
resolves

Interaction summary

SHALL support read, search-type.

Supported Profiles

ACP MedicalDevice Product ICDversion: 1.0.0-rc2)

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	type	`token`	The provider SHALL support the modifier `:in` to filter on codes defined in the ValueSet bound to type element in the ACP-MedicalDevice.Product-ICD profile.