Safeware: system safety and computers
Safeware: system safety and computers
Patterns in property specifications for finite-state verification
Proceedings of the 21st international conference on Software engineering
Little-JIL/Juliette: a process definition language and interpreter
Proceedings of the 22nd international conference on Software engineering
Flow analysis for verifying properties of concurrent software systems
ACM Transactions on Software Engineering and Methodology (TOSEM)
User guidance for creating precise and accessible property specifications
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Proceedings of the 30th international conference on Software engineering
Rigorously Defining and Analyzing Medical Processes: An Experience Report
Models in Software Engineering
Analyzing critical process models through behavior model synthesis
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
SEHC '09 Proceedings of the 2009 ICSE Workshop on Software Engineering in Health Care
Improving medical protocols by formal methods
Artificial Intelligence in Medicine
A benchmark for evaluating software engineering techniques for improving medical processes
Proceedings of the 2010 ICSE Workshop on Software Engineering in Health Care
Dynamic resource scheduling in disruption-prone software development environments
FASE'10 Proceedings of the 13th international conference on Fundamental Approaches to Software Engineering
Hi-index | 0.00 |
This paper provides an overview of the UMass/Baystate Medical Safety project, which has been developing and evaluating tools and technology for modeling and analyzing medical processes. We describe the tools that currently comprise the Process Improvement Environment, PIE. For each tool, we illustrate the kinds of information that it provides and discuss how that information can be used to improve the modeled process as well as provide useful information that other tools in the environment can leverage. Because the process modeling notation that we use has rigorously defined semantics and supports creating relatively detailed process models (for example, our models can specify alternative ways of dealing with exceptional behavior and concurrency), a number of powerful analysis techniques can be applied. The cost of eliciting and maintaining such a detailed model is amortized over the range of analyses that can be applied to detect errors, vulnerabilities, and inefficiencies in an existing process or in proposed process modifications before they are deployed.