entT ) : PatientT is a Patient of Doctor, TeleSvcDsk.online, DoctorT.AvailableForConsultation, PatientT.registered : pcd (consult administrator -> TeleSvcDsk, consultant -> DoctorT, consulter -> PatientT ) : consultation : eleSvcDsk.svcAccessed, DoctorT.consultationComplete, PatientT.consulted Figure 5.6 Example global policy rule with name PDP4_Rule1. The trigger T defines that the policy rule applies when the TeleSvcDsk composite role sends the RegistrationOK signal to the PatientT composite role. Furthermore, condition C states that the rule only applies when the instance playing the PatientT composite role is a Patient of the Doctor represented by the DoctorT composite role, DoctorT role is available, and that the Patient is registered. The action A then defines that the collaboration to be executed is consultation, with the TeleSvcDsk as consult administrator, the DoctorT as consultant, and the PatientT as consulter. Finally, the goal G states that the goal when executing the collaboration is for the TeleSvcDsk to access the services (e.g., patient journal), the DoctorT to complete the consulta- tion of PatientT, and PatientT to have been consulted (by the Doctor). responsible for enforcing the policy rule. For easier transformation from global to local policies, the condition is split into parts: one condition relating the roles, and one condition for each of the composite roles involved. The action A defines the collaboration use to be performed when the trigger event has occurred, given that the constraints in the condition hold. The action also defines the necessary role bindings from elementary (or subcomposite) roles to composite roles. The goal G defines the desired result of the action when the policy is applied and is a Boolean predicate expressing when the goal is achieved from the perspec- tive of the elementary collaboration as a whole. To allow for deriving the role goals for each of the policies that will follow the roles in the local PESMs, the goal of a composition policy rule is split into p