Proposed Wording: Add - Consent.rule Definition: 0..* rules engine computable policies, which together comprise the adjudicated mix of all the rules in all merged consent policies governing this Consent Directive.

Type = uri

Comment:

The FHIR Consent Directive profile supported conveyance of 0..* ConsentDirective.rules in additional to conveying the consent policies upon which it is based. An important consideration is that the adoption rate for even the most widely known of the rules language in healthcare space, XACML, is very low and is not likely to increase because of its costly overhead, and because it is not necessary e.g., for manual consent directive processing or where there is sufficient incorporation of consent policy compliance requirements in the domain's trust framework, that it is unnecessary to specify these rules when exchanging Consent Directives.

Requiring the use of one rules engine standard's representation of one, and mash up of more than one consent policies is a non-starter from a policy, implementation, and adoption perspective. Given that this is the route that the IHE APPC has taken, there is no reason for HL7 to follow the same path especially given its obvious flaws.

Summary:

Need Consent.rule