Arkansas cap on Medicaid therapy benefit to maintain ‘program integrity’

2016 ◽  
Vol 26 (38) ◽  
pp. 1-7
Author(s):  
Valerie A. Canady
Keyword(s):  
Program Integrity

Calculating Quantitative Integrity and Secrecy for Imperative Programs

2015 ◽  
Vol 6 (2) ◽  
pp. 23-46
Author(s):  
Tom Chothia ◽  
Chris Novakovic ◽  
Rajiv Ranjan Singh
Keyword(s):  
Mutual Information ◽  
Information Flow ◽  
Quantitative Information ◽  
Error Correcting Codes ◽  
Conditional Mutual Information ◽  
Program Integrity ◽  
Data Contamination ◽  
Definition Of ◽  
Quantitative Information Flow ◽  
Libor Rate

This paper presents a framework for calculating measures of data integrity for programs in a small imperative language. The authors develop a Markov chain semantics for their language which calculates Clarkson and Schneider's definitions of data contamination, data suppression, program suppression and program transmission. The authors then propose their own definition of program integrity for probabilistic specifications. These definitions are based on conditional mutual information and entropy; they present a result relating them to mutual information, which can be calculated by a number of existing tools. The authors extend a quantitative information flow tool (CH-IMP) to calculate these measures of integrity and demonstrate this tool with examples including error correcting codes, the Dining Cryptographers protocol and the attempts by a number of banks to influence the Libor rate.

A Scheme for Usage Integrity

1987 ◽  
Vol 26 (02) ◽  
pp. 69-72
Author(s):  
D. Fenna
Keyword(s):  
Information Systems ◽  
Data Protection ◽  
Medical Information ◽  
Medical Information Systems ◽  
University Of Alberta ◽  
Program Integrity ◽  
The Subject ◽  
Data Program ◽  
The University

SummaryThe need for assured integrity and confidentiality in medical information systems has long been recognized and has been the subject of major international working conferences [4, 5]. Beyond the purely physical, the field of data protection is commonly recognized as being divided into data/program integrity and usage integrity. This paper addresses the latter, describing a sophisticated scheme developed at the University of Alberta and progressively implemented at several associated hospitals. The IFIP-IMIA WG4 conference of 1982 reported in its conclusions “a need for well defined and accurately described cases that can be used as a reference”; this paper offers one such case.

Sign in / Sign up

Export Citation Format

Share Document