You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that a Consented policy tends to be describing what is allowed if the patient Permits on that policy; what explains what happens when the patient indicated Deny on that policy?
In the paper world, the given policy that the Consent points at has human language to express both pathways.
But in the Permission resource today there is no way to indicate this decision branch.
Do we need to support this kind of a decision branching, or do we determine that this is a need that should be handled by a more dedicated standard to policy, such as XACML?
The text was updated successfully, but these errors were encountered:
Discussed in t-con. Seems the need is real, but is not a priority to Permission resource at this time. The need is best filled with other policy standards, or systems policy design (non exposed standards language).
Given that a Consented policy tends to be describing what is allowed if the patient Permits on that policy; what explains what happens when the patient indicated Deny on that policy?
In the paper world, the given policy that the Consent points at has human language to express both pathways.
But in the Permission resource today there is no way to indicate this decision branch.
Do we need to support this kind of a decision branching, or do we determine that this is a need that should be handled by a more dedicated standard to policy, such as XACML?
The text was updated successfully, but these errors were encountered: