Opasnet:Guidebook specification: Difference between revisions

From Opasnet
Jump to navigation Jump to search
(object comparison table for DALY added)
m (removed accesscontrol (no need?))
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<accesscontrol>Members of projects</accesscontrol>
'''Table of Contents for the Guidebook has been moved to: [[Guidebook]]
'''Guidebook specification''' describes the contents of the [[guidebook]] (to be developed).


==Table of Contents for the Guidebook==
'''Text about the process and product objects in risk/impact assessment and within the guidance system, including article templates, have been moved to: [[Heande:Guidance system development]]


Guidebook (product) 1
'''Discussion about the object types (process/product descriptions) at : [[Talk:Guidebook]]
#* Scope of the guidebook 9
#Assessment (universal product)
#* Scope. Why to do (impact) assessment 3, 6, 12
#*Definition
#**What is an impact assessment
#**Different assessments: HIA, RA, IA... 4-5 (possibly own articles)
#Impact assessment (product)
#* Scope:
#**Purpose, questions 27
#**Boundaries 29
#**Scenarios 30-33
#*Definition
#**Variables
#**Analyses
#*Result
#**Results
#**Conclusions
#Performing an impact assessment (process) 10
#*Scope: General methodology 10
#** description of methodology used 11
#*Definition
#**Phases of an impact assessment 16
#***Scoping an impact assessment 26
#***Applying general information
#***Drawing a causal diagram 34
#***Designing variables
#***Executing variables and analyses
#***[[Reporting an assessment]]
#Open participation in (risk) assessment (process) 8
#Causal diagram (product) 35
#Emissions (universal product)
#Exposures (universal product)
#Emission modelling (process) 36-39
#*Scope
#*Definition
#**How to model 37
#**Sectoral, spatial, and temporal resolution 38
#Source-to-exposure modelling (process) 40
#*Scope: purpose
#*Definition: Different types 41
#*See also: pointers to resource centre 42
#Exposure-response function (universal product) 44
#*Scope 45
#*Definition: Different types 46
#Exposure-response function modelling (process)
#*Scope
#*Definition: How can they be derived? 47-48
#Performing meta-analysis (process) 48
#Risk characterisation (process) 51
#*Scope
#*Definition: Selecting indicators 50
#Disability-adjusted life year (procuct) 52
#*Scope
#*Definition:
#** How are they derived 54
#**Alternatives 53
#Quality-adjusted life year (product) 52
#Risk perception (product) 55
#Multi-attribute utility analysis (process) 55
#Value judgement (product) 56
#Value-of-information analysis (process) 57
#Uncertainties (product)
#*Scope
#*Definition
#**Uncertainty of the result: parameter uncertainty
#**Uncertainty of the definition: model uncertainty
#**Uncertainty of the scope: relevance
#Uncertainty assessment (process) 39, 43, 49, 58, 65, 69
#*Scope
#*Definition
#**Qualitative methods eg pedigree matrix 71
#**Quantitative methods 72-73
#**When to use which method? 73
#Uncertainty tools (process) 76
#Propagating uncertainties (process) 72
#*Scope
#*Definition
#**Monte Carlo 72
#**Bayesian analysis 72
#Monetary value (product) 59
#*Scope: Why do we need monetary values 60
#**Boundaries: Why do we choose monetary values and not utility points? 61
#*Definition: How are monetary values derived 63
#Discounting (process?) 64
#Cost-benefit analysis (product) 62
#Reporting an assessment (process) 67
#*Scope
#*Definition
#**Reporting uncertainties 70, 73
#Stakeholder involvement (process) 68
#Impacts (product) 77
#*Scope
#*Definition
#** [[Health impacts]]
#** Global warming 78
#**Accidents 79
#**Exosystems and biodiversity 80
#Health impacts (universal product)
 
==Article templates==
 
What are processes and products?
 
The guidance system will be composed of pages related to processes, and pages related to products, perhaps complemented with a few so-called ‘glue pages’, which could contain information that is not easily captured in the process/product structure.
 
A process is a method (tool, model, calculation, formal discussion, etc) in which various inputs are formed into a new product; the output. A process is “something you do”.
 
A product is both the input as well as the output of a process, and is a representation of reality (it can – at least in theory – be validated against reality).
 
Processes can lead to various products and products can be developed in various processes (there is not necessarily a 1 -1 relationship between processes and products)
 
(I did not think at all about nice words for these definitions, because I’m quite sure KTL has them already!)
 
Process/ product structure in Intarese
 
Elements of the Intarese method as developed in SP1 relate to either a process, or a product, or both. The graph below gives an idea of processes and products as developed in the Intarese project (graph should be improved/updated, if we want to present such a graph!) . For all processes and products, information needs to be provided in the guidance system.
 
When there is a clear 1 – 1 relationship between process and product (eg DALY process – DALY product), we will only ask for description of either process or product, in order to avoid confusion.
When there is no such direct 1 – 1 relationship, we will ask for separate description of process and product. An example of this is the process meta analysis, and the product exposure response function (ERF). Even though the process of meta analysis can lead to an estimation of the ERF, the meta analysis can also lead to an estimation of another product (eg severity weight), and an ERF (the product) can also be derived from another process (eg expert judgment).
 
How should an article about disability-adjusted life years be structured? The question is not at all obvious, so the different options are tested here. Discussion about the goodness of approaches is welcome. The following parts are repeated several times in the table; therefore, they are listed here and only referred to in the table.
;Purpose: DALY translates the impacts of diseases into life years based on their severity and duration, so that different diseases can be measured using a single currency, the life year. DALYs are based on disease-specific weights. (In contrast, QALYs evaluate the quality of life in a certain health state, not disease.)
;Formula: DALY = person-time lived * severity weight of the disease * (1- the duration of the disease as fraction of time)
: the severity weights for diseases come from the variable [[Variable:Disability-adjusted weights for diseases]]
 
In this ontology, the scope can be seen as a research question. The answer to this question is the result, and the definition tells how this result can be achieved.
 
{| {{prettytable}}
!Approach
!Scope
!Definition
!Result
|-----
!Variable (product object)
|'''DALY''' is a summary measure of burden of disease adding up increased mortality (years of life lost) and years lived with disability. '''Purpose''' <br>
'''The research question:''' What is the average DALY per person?
|Subattributes: Data tells about what data there exists about DALY estimates and gives links to the most important publications. Causality lists the upstream variables mentioned in the formula (see below). Unit is life-year. Formula is the '''formula'''.
|Result gives estimates for DALYs. However, the research question does not fulfil the clairvoyant criteria (or, it can be thought to apply to each individual in the world!) Therefore, only a few most important results (if any) can be mentioned here for illustration.
|-----
!Method (process object)
|'''DALY estimation''' is a process for measuring summarised burden of disease adding up increased mortality (years of life lost) and years lived with disability. '''Purpose''' <br>
'''The research question:''' What is a good way to estimate DALYs?
|The definition contains the reasoning and motivation for calculating DALYs. It compares and discusses different alternatives. It contains links to methodology articles. It is also open for comments and further developments.
|The result describes the state-of-the-art method and formulas such as the '''formula'''. The result is based on the content of the definition. Sub-attributes include input (the upstream variables), procedure (the calculations), and output (format of the process output).
|-----
!Class (product object)
|This '''DALY''' class describes the common properties of all objects that share this key property: The object is a summary measure of burden of disease adding up increased mortality (years of life lost) and years lived with disability. '''Purpose''' <br>
'''The research question:''' What are the common properties of all objects that fulfil the key property?
|Definition describes all other common properties of these objects. It also includes the discussions about the properties and whether they really are common to the objects. The most important property is the '''formula'''.
|The result contains a list of all objects (mainly variables) that belong to this class, i.e. variables that use DALYs to measure summary health impacts.
|-----
!Universal (product object)
|The '''kind of DALY''' describes the essence of DALY objects: a DALY object is a summary measure of burden of disease adding up increased mortality (years of life lost) and years lived with disability. '''Purpose'''
:{{comment|#1: |Maybe an universal (as defined by Loew) is actually the scope and definition attributes of a class, while the class (as defined mathematically as a particular kind of set) is the result attribute of the same object. In this way, Loew is happy, because we separate universals and classes and give the universal a stronger epistemological weight.|--[[User:Jouni|Jouni]] 00:45, 13 January 2008 (EET)}}
|Definition describes other properties of the "kind of DALY". The most important property is the '''formula'''.
:{{comment|#1: |With universals, the distinction between the scope and definition is not clear?|--[[User:Jouni|Jouni]] 00:45, 13 January 2008 (EET)}}
|Not relevant for universals?
|}
 
===Conclusions===
 
#Of these possibilities, the process seems to be the most suitable object for DALY.
#The '''purpose''' of all processes is to describe a good process for achieving the outcome described in the '''scope'''.
#The '''definition''' of a process describes the information you need to understand whether some process is suitable and good for the purpose. The scope and definition together form the structure of the process (in the same way as with variables).
#The '''result''' describes the state-of-the-art method for fulfilling the purpose.
#The class cannot be used here, because it is not clear how that would be applied in practical assessments. The common properties in the definition do not necessarily form a whole method that can be applied.
 
Example: products and processes in Intarese guidance system
 
 
===Template: process===
 
;Summary: The summary of a process is a very short overview of the process, and may contain all types of information that are considered relevant for this specific process (max words: …?)
;Name: The name of the process should be unique (there should not be two processes with identical names). The name should be chosen so that it is descriptive, unambiguous and not easily confused with other products/ processes. (max words: …?)
;Scope: The scope of the process describes its purpose: what is the process to be used for? This includes a verbal definition of the process and its expected output, including – if applicable – its spatial, temporal, or other limits (system boundaries). (max words: …?)
:This section may contain a link (more?) to further background information about the process, eg its history, current practice, etc) (or where do we put this background info?)
;Definition: The actual process – how it works – is described in the process’ definition. It consists of sub-attributes to describe the causal relations, data used to estimate the result, and the mathematical formula to calculate the result. The definition uses algebra or other explicit methods if possible. It also contains links top other processes or products that are related, or function as input to the process, as well as to the resource centre. (max words: …?)
;Results: The result section shortly describes the product of the process, which should match with the result as described in the scope. It furthermore links – if applicable – to the product. (max words: …?)
;See also: See also links to pages (both internal and external) which relate to the process subject. All subjects that could be relevant for readers of this page can be listed here.
;References: All references, as used in the texts above.
 
===Template: product===
 
;Summary: The summary of a product is a very short description of the product, and may contain all types of information that are considered relevant for this specific product (max words: …?)
;Name: The name of the product should be unique (there should not be two processes with identical names). The name should be chosen so that it is descriptive, unambiguous and not easily confused with other products/ processes. (max words: …?)
;Scope: The scope of the product gives the exact definition of the product. This includes a verbal definition of the product, including – if applicable – its spatial, temporal, or other limits (system boundaries). (max words: …?)
This section may contain a link (more?) to further background information about the product, eg its history, current practice, etc) (or where do we put this background info?)
;Definition: This section links to the process(es) that (may) lead to this product, explaining shortly what these processes involve (max words: …?)
;Results: Leave this section out?
;See also: See also links to pages (both internal and external) which relate to the product. All subjects that could be relevant for readers of this page can be listed here.
;References: All references, as used in the texts above.

Latest revision as of 13:08, 13 March 2009

Table of Contents for the Guidebook has been moved to: Guidebook

Text about the process and product objects in risk/impact assessment and within the guidance system, including article templates, have been moved to:

Discussion about the object types (process/product descriptions) at : Talk:Guidebook