Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

ValueSet: R5PermissionRuleCombiningForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-permission-rule-combining-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Responsible: Security Computable Name: R5PermissionRuleCombiningForR4

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/permission-rule-combining|5.0.0 for use in FHIR R4.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/permission-rule-combining|5.0.0 as defined in FHIR R5 in FHIR R4.

The source value set is bound to the following FHIR R5 elements:

  • Permission.combining

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://hl7.org/fhir/ValueSet/permission-rule-combining|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4

References

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/permission-rule-combining version 📍5.0.0
    CodeDisplayDefinition
    deny-overridesDeny-overridesThe deny overrides combining algorithm is intended for those cases where a deny decision should have priority over a permit decision.
    deny-unless-permitDeny-unless-permitThe “Deny-unless-permit” combining algorithm is intended for those cases where a permit decision should have priority over a deny decision, and an “Indeterminate” or “NotApplicable” must never be the result. It is particularly useful at the top level in a policy structure to ensure that a PDP will always return a definite “Permit” or “Deny” result.
    ordered-deny-overridesOrdered-deny-overridesThe behavior of this algorithm is identical to that of the “Deny-overrides” rule-combining algorithm with one exception. The order in which the collection of rules is evaluated SHALL match the order as listed in the permission.
    ordered-permit-overridesOrdered-permit-overridesThe behavior of this algorithm is identical to that of the “Permit-overrides” rule-combining algorithm with one exception. The order in which the collection of rules is evaluated SHALL match the order as listed in the permission.
    permit-overridesPermit-overridesThe permit overrides combining algorithm is intended for those cases where a permit decision should have priority over a deny decision.
    permit-unless-denyPermit-unless-denyThe “Permit-unless-deny” combining algorithm is intended for those cases where a deny decision should have priority over a permit decision, and an “Indeterminate” or “NotApplicable” must never be the result. It is particularly useful at the top level in a policy structure to ensure that a PDP will always return a definite “Permit” or “Deny” result. This algorithm has the following behavior.

 

Expansion

This value set expansion contains 6 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/permission-rule-combining5.0.0  deny-overridesDeny-overridesThe deny overrides combining algorithm is intended for those cases where a deny decision should have priority over a permit decision.
http://hl7.org/fhir/permission-rule-combining5.0.0  deny-unless-permitDeny-unless-permitThe “Deny-unless-permit” combining algorithm is intended for those cases where a permit decision should have priority over a deny decision, and an “Indeterminate” or “NotApplicable” must never be the result. It is particularly useful at the top level in a policy structure to ensure that a PDP will always return a definite “Permit” or “Deny” result.
http://hl7.org/fhir/permission-rule-combining5.0.0  ordered-deny-overridesOrdered-deny-overridesThe behavior of this algorithm is identical to that of the “Deny-overrides” rule-combining algorithm with one exception. The order in which the collection of rules is evaluated SHALL match the order as listed in the permission.
http://hl7.org/fhir/permission-rule-combining5.0.0  ordered-permit-overridesOrdered-permit-overridesThe behavior of this algorithm is identical to that of the “Permit-overrides” rule-combining algorithm with one exception. The order in which the collection of rules is evaluated SHALL match the order as listed in the permission.
http://hl7.org/fhir/permission-rule-combining5.0.0  permit-overridesPermit-overridesThe permit overrides combining algorithm is intended for those cases where a permit decision should have priority over a deny decision.
http://hl7.org/fhir/permission-rule-combining5.0.0  permit-unless-denyPermit-unless-denyThe “Permit-unless-deny” combining algorithm is intended for those cases where a deny decision should have priority over a permit decision, and an “Indeterminate” or “NotApplicable” must never be the result. It is particularly useful at the top level in a policy structure to ensure that a PDP will always return a definite “Permit” or “Deny” result. This algorithm has the following behavior.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code