EHR implementation initiatives tend to be driven by the promise of enhanced integration and availability of patient data [ 4], by the need to improve efficiency and cost-effectiveness [ 5], by a changing doctor-patient relationship toward one where care is shared by a team of health care professionals [ 5], and/or by the need to deal with a more complex and rapidly changing environment [ 6].
Furthermore, even though the implementation of treatment was supposed to be driven by a rigid set of rules, there was ambiguity in the discrepancy between what was required by the patients and how the treatment was provided by health personnel.
However, these values seem to be driven by an implementation complexity criterion rather than by an optimality one, since performance studies accomplished up to now have not considered the channel time variation effect [8, 9].
In addition, implementation will be driven by patient and healthcare providers' demand for the technologies, and payers' willingness to reimburse for genomic testing and counseling.
Research work programmes can thus become subject to, or be driven by, implementation imperatives.
28 Hence, our assumption for testing is that the implementation of change in a network will be driven by the collective reflection on feedback about the network.
The move away from the 'one-size-fits-all' model imposed by schema2.4 to a more modular, flexible approach, with supporting tools for implementation, has been driven by challenges in the general areas listed below in approximate order of importance: Content Model (what elements are allowed as children of which elements).
This shift to all software implementations is being driven by operators within the NFV (Network Functions Virtualization) initiative, and SDN is likely to play an enabling role in providing programmable, dynamic connectivity between the NFV instances.
In Kisii, programme implementation was driven by action research, and this allowed the intervention to be adapted to the local environment.
