Miksch S, Shahar Y, et al. Asbru: A task-specific, intention-based, and time-oriented language for representing skeletal plans. Proc. Seventh Workshop on Knowledge Engineering Methods and Languages (KEML-97) (Milton Keynes, UK, 1997).  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... that do not contain data of a particular patient, but that specify a general procedure; what parts of the plan are to be performed and how is decided as soon as the data of a patient is known) It was developed by Silvia Miksch together with Yuval Shahar and Peter Johnson [Miksch et al. 1997a, Miksch et al. 1997b, Shahar et al. 1998] The BNF definition of Asbru consists of over 100 non terminal symbols, and so is huge compared to most programming languages. But because it is not a general purpose language, it includes a lot of task specific parts that would otherwise need to be expressed by means of a ....

....here, because these features must be captured by the user interface called AsbruView, that is presented in the second part. 2.1 Basic Concepts These are the basic concepts that Asbru is made up of. An in depth description of all the fine points of Asbru is beyond the scope of this thesis (see [Miksch et al. 1997b] for example) 2.1.1 Hierarchical Decomposition A plan consists of sub plans that give its contents in greater detail. This is called decomposition. Thus, one can define a plan once at a more abstract level, and then refine it. 1 http: www.ifs.tuwien.ac.at asgaard 2 Many of the names in ....

[Article contains additional citation context not shown here]

Silvia Miksch, Yuval Shahar, and Peter Johnson (1997b). Asbru: A TaskSpecific, Intention-Based, and Time-Oriented Language for Representing Skeletal Plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Milton Keynes, UK, Open University.

....framework specification in the time oriented planning domain, called The Asgaard Project . It deals with different aspects of planning, by developing problem solving methods (PSM) to support human actors during planning work. These PSM are based on a plan description language called Asbru [10] to enable the acquisition of computer readable medical guidelines. Those guidelines are established in wide areas of medical care, but often only in a human readable format. Asbru shall make semantic information accessible to automated computation [9] 1 In Norse mythology, Asbru (or Bifrost) ....

S. Miksch, Y. Shahar, and P. Johnson. A Task-Specific, Intention-Based, and Time-Oriented Language for Representing Skeletal Plans. 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97), 1997.

....and has to be awaited before the MLM is actually started [10] The time delay statement may consequently be used to specify minimum duration constraints between individual MLMs. An approach that emphasizes efficient handling of temporal expressions within guideline knowledge is the Asbru language [15], which was created as part of the Asgaard project [24] Asbru provides the most powerful functionality in specifying temporal scheduling constraints in comparison with the above mentioned approaches. As we will demonstrate in greater detail in section 3.2.1, Asbru allows uncertain specification ....

....is investigated with the purpose of supporting the execution of clinical guidelines [24] As a foundation for the associated taskspecific problem solving methods, the time oriented, intention based language Asbru has been developed. It uses plans as the basic structure for representing guidelines [15]. Among the full set of Asbru language elements, containing knowledge classes such as preferences, intentions, conditions and effects, the time annotation and plan body constructs are of particular interest in our context. 3.2.1 Time annotations The general purpose of a time annotation is to ....

[Article contains additional citation context not shown here]

S. Miksch, Y. Shahar and P. Johnson, Asbru: A task-specific, intention-based, and timeoriented language for representing skeletal plans, in: Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97), Milton Keynes, UK (1997).

....We analyzed the diagramming formalism proposed by the Society for Medical Decision Making [6] and formalisms of a number of different guideline modeling methodologies. They included EON [5] an architecture for creating guideline based decisionsupport system developed at Stanford University; Asbru [7], a task based guideline modeling and execution architecture jointly developed in Austria and Israel; GUIDE [4] a guideline modeling methodology developed at University of Pavia; PRODIGY3 [2] the third phase of the University of Newcastle s primary care guideline modeling and execution system; ....

....modeled separately in scenario specific consultation templates that specify conditional actions. These actions are applicable before the provider makes a choice among treatment alternatives. Plans In contrast to PROIDGY3, where modeling decisionmaking in alternative scenarios is paramount, Asbru [7] adopts a model of processes for guidelines that emphasizes the flow of activities. Inspired by artificial intelligence work on planning, Asbru considers guidelines to be skeletal plans that are recursively refined into subplans. Plans are annotated by intentions (temporal patterns of actions and ....

Miksch, S, Shahar, Y, and Johnson, P. Asbru: A Task-Specific, Intention-Based, and TimeOriented Language for Representing Skeletal Plans. 7th Workshop on Knowledge Engineering: Methods & Languages (KEML97) . Milton Keynes, UK, 1997.

....work for our tools; Section IV describes the Guideline Markup Tool and shows how it can be used; Section V introduces the PIXEE XML editor; Section VI describes a scenario to demonstrate the use of the presented tools. We end up with conclusions in Section VII. II. THE ASBRU LANGUAGE Asbru [8] [9], 13] is a plan representation language that is used in the Asgaard Project to represent clinical guidelines as time oriented, skeletal plans. It can be used to express clinical protocols as skeletal plans [2] that can be instantiated for every patient. In Asbru, the following parts of a plan ....

Silvia Miksch, Yuval Shahar, and Peter Johnson. Asbru: A taskspecific, intention-based, and time-oriented language for representing skeletal plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Milton Keynes, UK, Open University, 1997.

.... is needed, which results in intertwining design time tasks and execution time tasks [Miksch, 1999] THE ASGAARD FRAMEWORK Plan Representation: Asbru To represent the clinical protocols, we have developed a time oriented, intention based, skeletalplan specification language, called Asbru [Miksch, et al. 1997] [Seyfang, et al. 2000] Clinical protocols are represented as time oriented, skeletal plans. Skeletal plans are plan schemata at different levels of detail, which capture the essence of the procedure, but leave enough room for execution time flexibility in the achievement of particular goals ....

Miksch, S., Shahar, Y. & Johnson, P.: Asbru: A Task-Specific, IntentionBased, and Time-Oriented Language for Representing Skeletal Plans, In Motta, E., van Harmelen, F., et al. (eds.), Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97), Milton Keynes, UK, January 22-24, The Open University, Milton Keynes, UK, pp. 9/1-9/20, 1997.

....problems in the last section. THE PROBLEM In this section, we first describe the reason, why we need a graphical representation of a complex notion of time, and then present a detailed list of requirements. Asbru s Time Annotation We are using a plan representation language called Asbru [9] for specifying medical therapy plans. One of the main components of this language are time annotations: A time annotation is used for limiting the time span of a plan or one of its components (like a condition or an intention) It consists of the following parts, any subset of which (except the ....

Miksch, S., Shahar, Y. & Johnson, P.: Asbru: A TaskSpecific, Intention-Based, and Time-Oriented Language for Representing Skeletal Plans, In Motta, E., van Harmelen, F., et al. (eds.), Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97), Milton Keynes, UK, January 22-24, The Open University, Milton Keynes, UK, pp. 9/1-9/20, 1997.

....assisting the medical staff in implementing them. In this section, a short overview over some of the key features of Asbru is given. A thorough introduction is far beyond the scope of this paper; please refer to [1] for more information. We are using a plan representation language called Asbru [2] for specifying medical protocols. Each protocol is translated into many Asbru plans therefore, we use the term plan instead of protocol in this paper. An Asbru plan can have subplans. If it does, its type specifies how its subplans are arranged in time. The type can be sequential, parallel, ....

Miksch S, Shahar Y, and Johnson P. Asbru: A TaskSpecific, Intention-Based, and Time-Oriented Language for Representing Skeletal Plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Milton Keynes, UK, Open University, 1997.

....they assume instantaneous actions and e#ects; they neglect that actions often are continuous #durative# and mighthave delayed e#ects and temporally extended goals; they overlook that unobservable underlying processes determine the observable state of the world#. A more detailed review is given in #Miksch et al. 1997#. On the other hand, workers in Medicine and Medical Informatics have recognized the importance of protocolbased care to ensure a high quality of care. An important approachwas the de#nition of the Arden syntax #Hripcsak et al. 1994#, which encodes situation action rules. This syntax has ....

.... called an action is found. This is called a semantic stop condition for the decomposition of plans. All the subplans consist of the same components as the plan, namely preferences, intentions, conditions, e#ects, and the plan body itself. An in depth discussion of Asbru can be found in #Miksch et al. 1997#. Asbru Syntax Plans in Asbru are written like in a programming language, as text that followsavery strict syntax. An example for a plan in Asbru syntax is given in Figure 1. Asbru for Users: AsbruView Its LISP like syntax makes Asbru easy to understand for people familiar with programming ....

Miksch, S., Shahar, Y., and Johnson, P. #1997#. Asbru: A task-speci#c, intention-based, and time-oriented language for representing skeletal plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages #KEML-97#. Milton Keynes, UK, Open University.

....of medical care. Such protocols are typically represented as text, tables, or ow charts. These representations are far from perfect, however, because they lack a clear concept of time and do not allow automation support for veri cation or quality assessment. In the Asgaard Asbru 1 project [12], a number of methods are being developed that deal with problems of clinical therapy planning. The key element of these e orts is Asbru, a powerful language to represent time oriented, skeletal plans. Asbru has a LISP like syntax, which makes it unusable for domain experts. Powerful methods are ....

....Asbru is a plan representation language that can capture time oriented, skeletal plans. In order to understand the speci c problems we faced in visualizing Asbru, one must be familiar with some of its basic concepts. These will be described here brie y. For a more detailed description, see [12]. Plan Layout (Actions) The plan body contains plans or actions that are to be performed if the preconditions hold. A plan is composed of other plans which must be performed in sequence, in any order, in parallel, or periodically (as long as a condition holds, a maximum number of times, and with ....

S. Miksch, Y. Shahar, and P. Johnson. Asbru: A task-specic, intention-based, and time-oriented language for representing skeletal plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Open University, Milton Keynes, UK, 1997.

....instead. Often, several different treatments or drugs have to be tried to find the best for a given patient. There are a number of ways to specify clinical protocols (e.g. flow charts, decision tables, etc. but they lack many features needed in this domain (for a more thorough discussion see [5, 6, 7]) Asbru is a language for specifying clinical protocols as time oriented, skeletal plans. In the Asgaard Project, we develop methods to support the design and execution of plans defined in Asbru 1 . In Asbru, it is possible to specify actions as well as conditions based on durations: a ....

....3. A comparison of AsbruView and Gantt and PERT charts is given in section 4. The results of a usability study of our AsbruView prototype are shortly discussed in section 5. 2. Asbru Basics A few of Asbru s basic concepts will be presented here briefly. For a more in depth discussion, please see [6, 7]. 1 Many of the names in the Asgaard project are based on names from Norse mythology. Asbru (also known as Bifrost) for example, is the rainbow bridge that leads to Asgaard, the home of the gods. Asbru allows the definition of plans that use other plans (similar to function calls in ....

S. Miksch, Y. Shahar, and P. Johnson. Asbru: A taskspecific, intention-based, and time-oriented language for representing skeletal plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Milton Keynes, UK, Open University, 1997.

....representation language Asbru. The visualization challenges Asbru poses are described in Section 3. Our answer to these challenges, AsbruView, is introduced in Section 4. We discuss the findings of a small study we did to assess AsbruView s usability in Section 5. 2 Introduction to Asbru Asbru [20, 21] is a plan representation language that is used in the Asgaard Project 1 to represent clinical guidelines as time oriented, skeletal plans. It can be used to express clinical protocols as skeletal plans [5] that can be instantiated for every patient (for an example see Fig. 1) In Asbru, the ....

S. Miksch, Y. Shahar, and P. Johnson. Asbru: A task-specific, intention-based, and timeoriented language for representing skeletal plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Milton Keynes, UK, Open University, 1997.

....of medical care. Such protocols are typically represented as text, tables, or ow charts. These representations are far from perfect, however, because they lack a clear concept of time and do not allow automation support for veri cation or quality assessment. In the Asgaard Asbru # project [12], a number of methods are being developed that deal with problems of clinical therapy planning. The key element of these e orts is Asbru, a powerful language to represent time oriented, skeletal plans. Asbru has a LISP like syntax, which makes it unusable for domain experts. Powerful methods are ....

....Asbru is a plan representation language that can capture time oriented, skeletal plans. In order to understand the speci c problems we faced in visualizing Asbru, one must be familiar with some of its basic concepts. These will be described here brie y. For a more detailed description, see [12]. #### ###### ########## The plan body contains plans or actions that are to be performed if the preconditions hold. A plan is composed of other plans which must be performed in sequence, in any order, in parallel, or periodically (as long as a condition holds, a maximum number of times, and with ....

S. Miksch, Y. Shahar, and P. Johnson. Asbru: A task-specic, intention-based, and time-oriented language for representing skeletal plans. In Proceedings of the 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97). Open University, Milton Keynes, UK, 1997.

No context found.

S. Miksch, Y. Shahar, and P. Johnson. Asbru: A task-speci#c, intention-based, and time-oriented language for representing skeletal plans. 7th Workshop on Knowledge Engineering: Methods and Languages #KEML-97#, pages 22#24, 1997.

No context found.

9-1 -- 9-20,.

No context found.

Miksch S, Shahar Y, et al. Asbru: A task-specific, intention-based, and time-oriented language for representing skeletal plans. Proc. Seventh Workshop on Knowledge Engineering Methods and Languages (KEML-97) (Milton Keynes, UK, 1997).

No context found.

Miksch, S, Shahar, Y, Johnson, P. Asbru: A taskspecific, intention-based, and time-oriented language for representing skeletal plans. 7th Workshop on Knowledge Engineering: Methods & Languages (KEML-97); 1997 Milton Keynes, UK. 9-1-9-20.

No context found.

Miksch S, Shahar Y, Johnson P. Asbru: A task-specific, intention-based, and time-oriented language for representing skeletal plans. In: Motta E, Harmelen FV, Pierret-Golbreich C, Filby I, Wijngaards N (eds). Proceedings of the Seventh Workshop on Knowledge Engineering: Methods & Languages. The Open University, Milton Keynes, 1997: 9.1--9.20.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC