Tsipi Heart | Ono Academic College (original) (raw)
Papers by Tsipi Heart
Journal of Information Technology Theory and …, Jan 1, 2001
Heart T. and N. Pliskin, Is E-Commerce of IT Application Services (ASP) Alive and Well? The Jou... more Heart T. and N. Pliskin, Is E-Commerce of IT Application Services (ASP) Alive and Well? The Journal of Information Technology Theory and Application (JITTA), 3:4, 2001, 33-41. ... IS ECOMMERCE OF IT APPLICATION SERVICES (ASP) ... TSIPI HEART, Ben-Gurion ...
Medical Decision Making, 2011
A health maintenance organization (HMO) provides physicians with electronic notifications regardi... more A health maintenance organization (HMO) provides physicians with electronic notifications regarding HMO-recommended drug substitutes. Investigating factors affecting physicians' compliance and evaluating associated cost savings. A cross-sectional observational study of all physicians in the HMO's clinics from June 2005 to February 2006. Recording physician ID, initial drug choice, final drug choice, elapsed time between initial and final choices, and pharmacological details. Out of 2120 physicians, 647 physicians met the inclusion criteria. They prescribed 1.21 million prescriptions. Transparently recording physicians' response to HMO-recommended drug substitutes within a drug-prescription sub-system of an electronic medical record. Compliance pattern, factors affecting compliance, and cost savings associated with compliance. Thirty percent of prescriptions did not comply with substitute recommendations. Compliance was most strongly affected by the substitute type, whether generic or therapeutic. Physician workload and age were found second and third in effect magnitude. Compliance was found to be non-automatic, selective and deliberate, suggesting that maintaining quality of care guides physicians in the prescription process. At least 4% of costs for prescribed drugs were saved as a result of compliance with substitute recommendations. Physicians selectively complied with electronic recommendations to substitute less costly for more costly drugs. Compliance was neither automatic nor thoughtless and entailed cost containment with possibly marginal compromise on quality of care or none at all, as compliance mostly involved substituting generic for patent drugs. We strongly feel that the results can be generalized to other HMOs as well.
Journal of Cases on Information Technology, 2000
International Journal of Reliable and Quality E-Healthcare, 2016
Israel Journal of Health Policy Research, 2015
Patient Education and Counseling, 2013
ICIS 2009 Proceedings, 2009
Journal of Systems and Information Technology, 2009
Purpose–The limited success of electronic health records (EHRs) implementation in the healthcare ... more Purpose–The limited success of electronic health records (EHRs) implementation in the healthcare services in general, and a national EHR in particular, requires better understand and documentation of the current drivers and inhibitors of EHR adoption, together with a ...
ACM Sigmis Database, 2010
Software as a Service (SaaS) is a relatively new organizational application sourcing alternative,... more Software as a Service (SaaS) is a relatively new organizational application sourcing alternative, offering organizations the option to access applications--via the Internet--that are remotely hosted on offsite servers instead of installing equivalent applications in-house, thus presumably saving costs. Although SaaS has been offered since the late 1990s, so far it has not become a dominant sourcing alternative for organizational core
Journal of The Ais, 2011
Page 1. Volume 12 ▪ Issue 3 Jo u rn a lo f th e Asso c ia tio n fo r In fo rm a tio n Abstract Sp... more Page 1. Volume 12 ▪ Issue 3 Jo u rn a lo f th e Asso c ia tio n fo r In fo rm a tio n Abstract Special Issue Tsipi Heart Ben-Gurion University of the Negev heart@bgu.ac.il Yisrael Parmet Ben-Gurion University of the Negev iparmet@bgu.ac.il ...
For nearly three decades the term "Test Case" (TC) has been widely used... more For nearly three decades the term "Test Case" (TC) has been widely used in software testing as a work unit, a metric and a documentation entity. A thorough review of the extant literature reveals that there is no formal and agreed-upon definition of a TC, in spite of its centrality and extensive use. Following Kaner's (2003) assertion that "good TC is one that gives the required information", we see benefits in formalizing a unified, well defined and structured TC format. In this paper we present a brief literature review of the TC concept, explore the definitions of TCs, propose a classification of the various definitions into four categories, and highlight the conceptualization underlying each category. Undesired implications of this situation are then discussed, and four criteria for a 'good' TC definition are proposed while discussing benefits entailed by such a definition. The paper proceeds by suggesting an alternative structural definition of a TC which complies with the above criteria. The proposed definition illustrates a TC as a composition of five structures. The first four are: TC factors, internal activities and flows, dynamic external interaction entities, and verification actions. A different, fifth structure is the TC output and results. We elaborate on the five structures, illustrate the definition and its benefits via the lens of the four criteria of a 'good' TC, and discuss its use in several applications showing that it addresses issues pertaining to various environments. In conclusion we discuss limitations and future research trajectories opened by the proposed TC definition, as well as its implications for practice.
Since the 1980s the term "Test Case" (TC) has been recognized as a building block for describing ... more Since the 1980s the term "Test Case" (TC) has been recognized as a building block for describing testing items, widely used as a work unit, metric and documentation entity. In light of the centrality of the TC concept in testing processes, the questions this paper attempts to answer are: What are the uses of TC in software testing? Is there a general, commonly agreed-upon definition of a TC? If not, what are the implications of this situation? This article reviews and explores the history, use and definitions of TCs, showing that while extensively used in research and practice, there is no one formal agreed upon definition of a TC. In this paper we point at undesirable implications of this situation, suggest four criteria for a ’good’ TC definition, and discuss the benefits accrued from such a definition. We conclude by urging the academic and professional community to formalize a TC definition for the benefits of the industry and its customers, and strongly believe that this review paves the way to articulating a formal TC definition. Such a definition, when widely accepted, will clarify some of the ambiguity currently associated with TC interpretation, hence with software testing assessment which relies on TCs as metrics. Furthermore, a formal definition can advance automation of TC generation and management.
This paper proposes the Basic Verification Action (BVA) structure to verify outcomes produced dur... more This paper proposes the Basic Verification Action (BVA) structure to verify outcomes produced during and at the end of test cases execution. BVA items are determined, stored and maintained as external entities to the actual test cases, forming a metadata repository comprised of a combination of technical and business knowledge of the software application. When applied to the final outcomes
Journal of Information Technology Theory and …, Jan 1, 2001
Heart T. and N. Pliskin, Is E-Commerce of IT Application Services (ASP) Alive and Well? The Jou... more Heart T. and N. Pliskin, Is E-Commerce of IT Application Services (ASP) Alive and Well? The Journal of Information Technology Theory and Application (JITTA), 3:4, 2001, 33-41. ... IS ECOMMERCE OF IT APPLICATION SERVICES (ASP) ... TSIPI HEART, Ben-Gurion ...
Medical Decision Making, 2011
A health maintenance organization (HMO) provides physicians with electronic notifications regardi... more A health maintenance organization (HMO) provides physicians with electronic notifications regarding HMO-recommended drug substitutes. Investigating factors affecting physicians' compliance and evaluating associated cost savings. A cross-sectional observational study of all physicians in the HMO's clinics from June 2005 to February 2006. Recording physician ID, initial drug choice, final drug choice, elapsed time between initial and final choices, and pharmacological details. Out of 2120 physicians, 647 physicians met the inclusion criteria. They prescribed 1.21 million prescriptions. Transparently recording physicians' response to HMO-recommended drug substitutes within a drug-prescription sub-system of an electronic medical record. Compliance pattern, factors affecting compliance, and cost savings associated with compliance. Thirty percent of prescriptions did not comply with substitute recommendations. Compliance was most strongly affected by the substitute type, whether generic or therapeutic. Physician workload and age were found second and third in effect magnitude. Compliance was found to be non-automatic, selective and deliberate, suggesting that maintaining quality of care guides physicians in the prescription process. At least 4% of costs for prescribed drugs were saved as a result of compliance with substitute recommendations. Physicians selectively complied with electronic recommendations to substitute less costly for more costly drugs. Compliance was neither automatic nor thoughtless and entailed cost containment with possibly marginal compromise on quality of care or none at all, as compliance mostly involved substituting generic for patent drugs. We strongly feel that the results can be generalized to other HMOs as well.
Journal of Cases on Information Technology, 2000
International Journal of Reliable and Quality E-Healthcare, 2016
Israel Journal of Health Policy Research, 2015
Patient Education and Counseling, 2013
ICIS 2009 Proceedings, 2009
Journal of Systems and Information Technology, 2009
Purpose–The limited success of electronic health records (EHRs) implementation in the healthcare ... more Purpose–The limited success of electronic health records (EHRs) implementation in the healthcare services in general, and a national EHR in particular, requires better understand and documentation of the current drivers and inhibitors of EHR adoption, together with a ...
ACM Sigmis Database, 2010
Software as a Service (SaaS) is a relatively new organizational application sourcing alternative,... more Software as a Service (SaaS) is a relatively new organizational application sourcing alternative, offering organizations the option to access applications--via the Internet--that are remotely hosted on offsite servers instead of installing equivalent applications in-house, thus presumably saving costs. Although SaaS has been offered since the late 1990s, so far it has not become a dominant sourcing alternative for organizational core
Journal of The Ais, 2011
Page 1. Volume 12 ▪ Issue 3 Jo u rn a lo f th e Asso c ia tio n fo r In fo rm a tio n Abstract Sp... more Page 1. Volume 12 ▪ Issue 3 Jo u rn a lo f th e Asso c ia tio n fo r In fo rm a tio n Abstract Special Issue Tsipi Heart Ben-Gurion University of the Negev heart@bgu.ac.il Yisrael Parmet Ben-Gurion University of the Negev iparmet@bgu.ac.il ...
For nearly three decades the term "Test Case" (TC) has been widely used... more For nearly three decades the term "Test Case" (TC) has been widely used in software testing as a work unit, a metric and a documentation entity. A thorough review of the extant literature reveals that there is no formal and agreed-upon definition of a TC, in spite of its centrality and extensive use. Following Kaner's (2003) assertion that "good TC is one that gives the required information", we see benefits in formalizing a unified, well defined and structured TC format. In this paper we present a brief literature review of the TC concept, explore the definitions of TCs, propose a classification of the various definitions into four categories, and highlight the conceptualization underlying each category. Undesired implications of this situation are then discussed, and four criteria for a 'good' TC definition are proposed while discussing benefits entailed by such a definition. The paper proceeds by suggesting an alternative structural definition of a TC which complies with the above criteria. The proposed definition illustrates a TC as a composition of five structures. The first four are: TC factors, internal activities and flows, dynamic external interaction entities, and verification actions. A different, fifth structure is the TC output and results. We elaborate on the five structures, illustrate the definition and its benefits via the lens of the four criteria of a 'good' TC, and discuss its use in several applications showing that it addresses issues pertaining to various environments. In conclusion we discuss limitations and future research trajectories opened by the proposed TC definition, as well as its implications for practice.
Since the 1980s the term "Test Case" (TC) has been recognized as a building block for describing ... more Since the 1980s the term "Test Case" (TC) has been recognized as a building block for describing testing items, widely used as a work unit, metric and documentation entity. In light of the centrality of the TC concept in testing processes, the questions this paper attempts to answer are: What are the uses of TC in software testing? Is there a general, commonly agreed-upon definition of a TC? If not, what are the implications of this situation? This article reviews and explores the history, use and definitions of TCs, showing that while extensively used in research and practice, there is no one formal agreed upon definition of a TC. In this paper we point at undesirable implications of this situation, suggest four criteria for a ’good’ TC definition, and discuss the benefits accrued from such a definition. We conclude by urging the academic and professional community to formalize a TC definition for the benefits of the industry and its customers, and strongly believe that this review paves the way to articulating a formal TC definition. Such a definition, when widely accepted, will clarify some of the ambiguity currently associated with TC interpretation, hence with software testing assessment which relies on TCs as metrics. Furthermore, a formal definition can advance automation of TC generation and management.
This paper proposes the Basic Verification Action (BVA) structure to verify outcomes produced dur... more This paper proposes the Basic Verification Action (BVA) structure to verify outcomes produced during and at the end of test cases execution. BVA items are determined, stored and maintained as external entities to the actual test cases, forming a metadata repository comprised of a combination of technical and business knowledge of the software application. When applied to the final outcomes