The consensus glossary of temporal database concepts — February 1998 version

Jensen, Christian S.; Dyreson, Curtis E.; Böhlen, Michael H.; Clifford, James; Elmasri, Ramez; Gadia, Shashi K.; Grandi, Fábio; Hayes, Patrick J.; Jajodia, Sushil; Käfer, Wolfgang; Kline, Nick; Lorentzos, Nikos A.; Mitsopoulos, Yannis; Montanari, Angelo; Nonen, Daniel; Peressi, Elisa; Pernici, Barbara; Roddick, John F.; Sarda, Nandlal L.; Scalas, Maria Rita; Segev, Arie; Snodgrass, Richard T.; Soo, Mike D.; Tansel, Abdullah Uz; Tiberio, Paolo; Wiederhold, Gio

doi:10.1007/bfb0053710

Cited by 285 publications

(175 citation statements)

References 0 publications

Supporting

Mentioning

167

Contrasting

Unclassified

Order By: Relevance

“…It is the time the guideline is considered in force by the medical community and, thus, is applied to patients. It has the same semantics of valid time as in temporal databases [20], since it represents the time the guideline actually belongs to the state-of-the-art of clinical practice. Efficacy time.…”

Section: Temporal Versioningmentioning

confidence: 99%

“…Both are necessary to correctly deal with cases as the one in the last described example: the guideline version G(v1) for the applicability context H can still be selected today as its efficacy includes current time, although its validity does not. Furthermore, in addition to the time dimensions which model the dynamics of guidelines in the real world, transaction time [20] plays an important role when automatic management of information through computer systems is involved and, thus, should never be neglected, since it allows to execute retro-or pro-active modifications and to keep track of their execution for audit purposes. For example, it might be the case that a physician makes a wrong decision in choosing a drug following the provisions of a guideline retrieved from the system when the returned consolidated version is actually out-of-date; the decision is taken while a modified version of the guideline (e.g.…”

Section: Temporal Versioningmentioning

confidence: 99%

See 1 more Smart Citation

A Personalization Environment for Multi-version Clinical Guidelines

Grandi

2011

Biomedical Engineering Systems and Technologies

Self Cite

View full text Add to dashboard Cite

Abstract. In this work, we introduce a personalization environment for the representation and efficient management of multi-version clinical guidelines. The environment is composed of an XML repository accessed through a personalization engine, which uses temporal perspective, patient profile and context information to reconstruct a guideline version tailored to a specific use case. In particular, we apply and extend to clinical guidelines solutions we previously developed for norm texts in the legal domain, and show how multi-version representation capabilities and personalization query facilities can be added to their management.

show abstract

Section: Temporal Versioningmentioning

confidence: 99%

Section: Temporal Versioningmentioning

confidence: 99%

A Personalization Environment for Multi-version Clinical Guidelines

Grandi

2011

Biomedical Engineering Systems and Technologies

Self Cite

View full text Add to dashboard Cite

show abstract

“…A WfMS is composed of a set of distributed sites S each of which has a single local clock. An concept of time [10] with the following characteristics is supported:…”

Section: Timestamps and Primitive Event Occurrencesmentioning

confidence: 99%

Semantics of reactive components in event-driven workflow execution

Tombros

Geppert

Dittrich

1997

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

View full text Add to dashboard Cite

Abstract:The exact semantics of workflows and involved processing entities is an open yet urgent problem. This paper considers the semantics and correctness of eventdriven workflow execution. The basis for the formalization in our approach is provided by an event history which records all events that have occurred during the execution of workflows. Workflows are executed by reactive components which operate on top of that history. Based on the history it is possible to determine the semantics of these reactive components (and consequently, the semantics of workflows) as well as to check whether their observable behavior is correct.

show abstract

“…According to the glossary [18], such constraints can be divided into three categories, to illustrate which we use the temporal data model in Fig. 1.…”

Section: Introductionmentioning

confidence: 99%

Complexity of Reasoning over Temporal Data Models

Artale

Kontchakov

Ryzhikov

et al. 2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. We investigate the computational complexity of reasoning over temporal extensions of conceptual data models. The temporal conceptual models we analyse include the standard UML/EER ISA between entities and relationships, disjointness and covering, cardinality constraints and their refinements, multiplicity and key constraints; in the temporal dimension, we have timestamping, evolution and transition constraints, as well as lifespan cardinalities. We give a nearly comprehensive picture of the impact of these constraints on the complexity of reasoning, which can range from NLOGSPACE to undecidability.

show abstract

The consensus glossary of temporal database concepts — February 1998 version

Cited by 285 publications

References 0 publications

A Personalization Environment for Multi-version Clinical Guidelines

A Personalization Environment for Multi-version Clinical Guidelines

Semantics of reactive components in event-driven workflow execution

Complexity of Reasoning over Temporal Data Models

Contact Info

Product

Resources

About