Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

Test : PPQm_Delete a policy (PPQ-3/4)

Test Summary

Id
13659
Keyword
PPQm_Delete a policy (PPQ-3/4)
Name
PPQm_Delete a policy (PPQ-3/4)
Version
Bern 2024
Test Author
vhofman
Last modifier
Angelina.Ker
Status
ready
Type
connectathon
Is external tool ?
Is Orchestrable
is Validated ?
Peer Type
Peer To Peer
Short Description
Delete an existing Policy in the Policy Repository
Last changed
9/4/24 11:35:21 AM

Test Description in English

Short Description

The purpose of this test is to add a delete an existing Policy to the Policy Repository with PPQ-3 and PPQ-4 transactions.

Goal

This test verifies the required steps for a Policy Source to delete an existing Policy in the Policy Repository

Tested Components

  • Policy Source
  • Policy Repository 

Prerequisite

The Mobile Privacy Policy Feed needs TLS for the communication. Make sure that this option is set in your configuration for Proxy.

  • You SHALL have a partner to perform this test.
  • You can find samples of PPQm consents here.
  • Bundles and consents have to be compliant with these implementation guides :

The PPQ-3/4 transactions SHALL record the events using ATX:FHIR Feed option (RESTful).

Description

The Policy Source sends a DeletePolicy request to the Policy Repository. This request is used to delete policies in the Policy Repository.


Evidence

The Policy Source shall present the following evidence:

  • The Policy Source sends a Consent delete request to the Policy Repository of the community.
  • The Consent delete request must delete an existing policy in the Policy Repository of its community.
  • The PPQ-3 response must be consistent with a success message.
  • The Policy Source sends a Consent Bundle delete request to the Policy Repository of the community.
  • The Consent Bundle delete request must delete at least an existing policy in the Policy Repository of its community.
  • The PPQ-4 Bundle response must be consistent with a success message. 

Evaluation

In order to verify the test the Connectathon monitor will ask for the queries and responses of the DeletePolicy requests.



Test Roles

Keyword
# to realize
Card Min
Card Max
Optionality
URL
URL Doc
PPQm_SOURCE
Integration profileActorOptionIs tested ?
Keyword
Keyword
Keyword
Keyword
IntegrationProfile CH:PPQm-Privacy Policy Query for MobileActor POLICY_SRC-Policy SourceNONEtrue
111Required
PPQm_REPOSITORY
Integration profileActorOptionIs tested ?
Keyword
Keyword
Keyword
Keyword
IntegrationProfile CH:PPQm-Privacy Policy Query for MobileActor POLICY_REPO-Policy RepositoryNONEtrue
111Required

Test Steps


Step Index
Initiator Role
Responder Role
Transaction
Secured
Message Type
Option
Description
Assertions
1PPQm_REPOSITORYPPQm_REPOSITORYNoneRequiredTo ease validation, please use the gazelle proxy with this test.
10PPQm_SOURCEPPQm_SOURCENoneRequiredPrepare your requests to the Policy Repository
20PPQm_SOURCEPPQm_REPOSITORYPPQ-3HTTP DELETERequiredThe Policy Source sends an Delete Policy Set.
30PPQm_SOURCEPPQm_SOURCENoneRequiredPaste in this step request and response received evidences.
40PPQm_SOURCEPPQm_REPOSITORYPPQ-4HTTP POSTRequiredThe Policy Source sends at least 1 Delete Policy Set embedded in a Bundle.
50PPQm_SOURCEPPQm_SOURCENoneRequiredPaste in this step request and response received evidences.

Tool index

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top