Femurkop necrose na mediale collumfracturen met het accent op de vroegdiagnostiek

Contains fulltext : MMUBN000001_211760331.pdf (publisher's version ) (Open Access)Proefschrift Katholieke Universiteit Nijmegen112

Progress with formalization in medical informatics?

The prevailing view of medical informatics as a primarily subservient discipline in health care is challenged. Developments in both general informatics and medical informatics are described to identify desirable properties of modeling languages and tools needed to solve key problems in the application field. For progress in medical informatics, it is considered essential to develop far more formal modeling languages, modeling techniques, and tools. A major aim of this development should be to expel ambiguity from concepts essential to medicine, positioning medical informatics "at the heart of health care.

Requirements for medical modeling languages.

OBJECTIVE: The development of tailor-made domain-specific modeling languages is sometimes desirable in medical informatics. Naturally, the development of such languages should be guided. The purpose of this article is to introduce a set of requirements for such languages and show their application in analyzing and comparing existing modeling languages. DESIGN: The requirements arise from the practical experience of the authors and others in the development of modeling languages in both general informatics and medical informatics. The requirements initially emerged from the analysis of information modeling techniques. The requirements are designed to be orthogonal, i.e., one requirement can be violated without violation of the others. RESULTS: The proposed requirements for any modeling language are that it be "formal" with regard to syntax and semantics, "conceptual," "expressive," "comprehensible," "suitable," and "executable." The requirements are illustrated using both the medical logic modules of the Arden Syntax as a running example and selected examples from other modeling languages. CONCLUSION: Activity diagrams of the Unified Modeling Language, task structures for work flows, and Petri nets are discussed with regard to the list of requirements, and various tradeoffs are thus made explicit. It is concluded that this set of requirements has the potential to play a vital role in both the evaluation of existing domain-specific languages and the development of new ones