Mapping between PpqmConsent Resources and CH:PPQ Policy Sets

Transformation of PpqmConsent Resources into CH:PPQ Policy Sets

Each PpqmConsent resource contains an element identifier with type.coding.code equal to “templateId”. In this element, the attribute value contains the ID of the official Policy Stack template. For example:

{ 
  "type": {
    "coding": [{
      "system": "http://fhir.ch/ig/ch-epr-fhir/CodeSystem/PpqmConsentIdentifierType",
      "code": "templateId"
    }]
  },
  "value": "201" 
}

The PPQ-conformant XACML 2.0 Policy Set SHALL be created according to this template. Thereby, the value placeholders SHALL be filled according to the table below:

Table 1: Mapping of PpqmConsent attributes onto CH:PPQ policy set template placeholders

Transformation of CH:PPQ Policy Sets into PpqmConsent Resources

Each patient-related CH:PPQ policy set is generated from a template provided in the official Policy Stack, but does not hold a direct reference to this template. Therefore, the first step is to determine the template ID. For that, the following heuristics SHALL be used:

• The policy set contains an element /PolicySet/Target/Subjects with three sub-elements Subject → template 203.
• The policy set contains an element /PolicySet/Target/Subjects/Subject/SubjectMatch/AttributeValue/CodedValue with @codeSystem equal to “2.16.756.5.30.1.127.3.10.6” and:
  • @code equal to “PAT” → template 201.
  • @code equal to “REP” → template 303.
• The policy set contains an element /PolicySet/Target/Subjects/Subject/SubjectMatch/AttributeValue/CodedValue with @codeSystem equal to “2.16.756.5.30.1.127.3.10.5” and @code equal to “EMER” → template 202.
• The policy set contains an element /PolicySet/Target/Subjects/Subject/SubjectMatch/SubjectAttributeDesignator with @AttributeId equal to “urn:oasis:names:tc:xspa:1.0:subject:organization-id” → template 302.
• The ID of the referenced policy set (value of the element <PolicySetIdReference>) contains the substring “delegation” → template 304.
• Otherwise → template 301.

The PpqmConsent resource attributes SHALL be populated according to the rules defined for each template in the table below:

Table 2: Mapping of CH:PPQ policy set elements onto PpqmConsent attributes