Navigation
Home Search the siteThe project
Project overview The platform Medical background Partners Advisory Boards Work plan Deliverables Scientific papers Downloads Online demonstrators FAQNewsroom
All news Reaction in the press Events Clustering event Video archive Relevant links Event CalendarHONcode
This site complies with the HONcode standard for trust worthy health information:
verify here.
Affiliations
REACTION is affilliated with these programs and organisations:
REACTION is delivering better and more efficient healthcare services in Europe, thus supporting the Commissions activities in ICT for Health: eHealth.
The REACTION platform allows for the creation of inclusive applications with accessibility for all. The project supports the Commissions campaign: eInclusion - be part of it!
REACTION is delivering better and more efficient healthcare services in Europe, thus supporting the Commissions activities in ICT for Health: eHealth.
The REACTION platform allows for the creation of inclusive applications with accessibility for all. The project supports the Commissions campaign: eInclusion - be part of it!
Sign In
Facts
The REACTION project is a 4-year project started in 2010. It is partly funded by the European Commission under the 7th Framework Programme in the area of Personal Health Systems under Grant Agreement no. 248590
Impressum Privacy
Previous Newsletters
Read previous issues of our newsletter here:
April 2014
August 2013
June 2012
August 2011
April 2011
November 2010
Most Read...
Articles
| In-hospital saf... |
185170 |
| Reaction in the... |
111411 |
| Project overview |
104809 |
| Medical background |
104031 |
| Project methodo... |
78567 |
News
| Research award ... |
56048 |
| IST-Africa Call... |
52014 |
| REACTION at one... |
50035 |
| REACTION videos... |
48507 |
| REACTION online... |
47150 |
Popular Downloads
| REACTION brochure |
30121 |
| Design of a mobil... |
13007 |
| D9-4 Healthcare e... |
11056 |
| D9-2 Regulatory f... |
8387 |
| 2_Regulatory Fram... |
6506 |
Share this
eHealth at Facebook
Join the discussion on EC eHealth at Facebook!
Deliverables
The Reaction project has planned an extensive series of deliverables documenting the project results. A large number of these deliverables are available to the public and can be downloaded from the web site using the menu to the left. Please note, that access to the download area requres registration.
The following list containts deliverables planned up to and including M48 of the project.
| Deliverable No [1] |
Deliverable title | Delivery date [2] |
Nature [3] |
Dissemination level [4] |
Status |
| D1.1 | Project Initiation Document | M1 | R | CO | |
| D1.2 | Project Quality & Risk Management Plan | M1 | R | CO | |
| D1.3 | Quarterly progress reports for the commission | M3+3 | R | CO | |
| D1.4 | Plan for managing knowledge and intellectual property | M9 | R | CO | |
| D1.5 | Periodic activity, management and financial reports | M12+12 | R | CO | |
| D1.6 | Final report on activity, management and outcome | M48 | R | CO | |
| D2.1 | Scenarios for usage of HYDRA in 3 different domains | M5 | R | PU | |
| D2.2 | Initial technology watch report | M4 | R | PU | |
| D2.3 | Initial regulatory-standards watch report | M4 | R | PU | |
| D2.4 | Initial market watch report | M4 | R | CO | |
| D2.5 | Initial requirements report | M6 | R | RE | |
| D2.6 | Validation framework | M9 | R | RE | |
| D2.7 | Updated requirements report | M18, M30 | R | PU | |
| D2.8 | Updated watch report | M18, M30 | R | PU | |
| D3.1 | Existing applications, services, devices and standards | M5 | R | PU | |
| D3.2 | Updated systems requirement report | M12+6 | R | RE/PU | |
| D3.3 | Draft of architectural design specification | M8 | R | RE | |
| D3.4 | Initial architectural design specification | M18 | R | PU | |
| D3.5 | Updated State of the Art | M19 | R | RE/PU | |
| D3.6 | Data Acquisition Component Report | M20 | R | RE | |
| D3.7 | Grid Architecture Report | M21 | R | RE | |
| D3.8 | Context Awareness Report | M21 | R | RE | |
| D3.9 | Updated System Architecture Report | M22, M34 | R | RE | |
| D3.10 | Final Data Acquisition Report | M30 | R | RE | |
| D3.11 | Final Context Awareness Report | M30 | R | RE | |
| D4.1 | Technical requirements specification | M10 | R | PU | |
| D4.2 | Embedded service SDK prototype and report | M18, M24 | R | PU | |
| D4.3 | Self-* properties SDK prototype and report | M18, M30 | P | CO | |
| D4.4 | Embedded AmI components prototype | M20, M30 | P | CO | |
| D4.5 | QoS-enabled Hydra middleware | M24 | P | CO | |
| D5.1 | Communication infrastructure requirements | M7 | R | RE | |
| D5.2 | Wireless communications | M12 | P | RE | |
| D5.3 | Draft of Wireless Network Implementation Description | M18 | R | RE | |
| D5.4 | Draft of Wireless Devices Integration Description | M18 | R | RE | |
| D5.5 | Device-to-Device Communication | M18 | R | RE | |
| D5.6 | Draft of Network Security Implementation Description | M18 | R | RE | |
| D5.7 | Wireless Network SDK Prototype | M20 | P | RE | |
| D6.1 | Quality Attribute Scenarios – technical requirements | M17, M29 | R | RE | |
| D6.2 | MDA Design Document | M18 | R | PU | |
| D6.3 | Semantic Web Services Design document | M18 | R | PU | |
| D6.4 | Ontologies Prototype | M20 | P | RE | |
| D6.5 | SoA middleware components prototype | M20 | P | RE | |
| D7.1 | Updates of security requirement specification | M20, M28 | R | RE | |
| D7.3 | Security architectural models design specification | M17 | R | RE | |
| D7.4 | Enhanced Prototypes of security & privacy managers | M14, M22 | P | RE | |
| D7.5 | Hydra Security Meta Model (update of D7.2) | M23 | R | RE | |
| D7.6 | Impact of architectural security implications (update of D7.3) | M24 | R | RE | |
| D8.1 | Test Plan | M10 | R | RE | |
| D8.2 | Integration Plan | M20 | R | RE | |
| D8.3 | Integrated Platform for SDK Demonstrator | M22 | R | RE | |
| D9.1 | Hydra middleware development platform | M8 | P | CO | |
| D9.2 | Application one prototype requirements | M8 | R | PU | |
| D9.3 | Application two prototype requirements | M12 | R | PU | |
| D9.4 | Application three prototype requirements | M12 | R | PU | |
| D9.5 | Application one demonstrator (Proof of concept) | M12 | P | CO | |
| D9.6 | SDK Demonstrator | M24 | P | CO | |
| D10.1 | Validation Plan for Demonstrators | M20 | R | PU | |
| D10.2 | Validation Report for SDK Demonstrator | M26 | R | PU | |
| D10.3 | Validation Report for DDK Demonstrator | M38 | R | PU | |
| D10.4 | Validation Report for IDE Demonstrator | M48 | R | PU | |
| D10.5 | Business modelling concepts | M18 | R | RE | |
| D10.6 | Business models for Hydra middleware | M30 | R | RE | |
| D12.1 | Internal technology workshops teaching material | M4 | R | RE | |
| D12.2 | External developers workshops teaching material | M18 | R | PU | |
| D12.3 | External business modelling teaching material | M18 | R | PU | |
| D12.4 | Combined Internal Training Material | M24 | R | RE | |
| D12.5 | External developers workshops teaching material | M30 | R | RE | |
| D13.1 | Project website | M3 | P | PU | |
| D13.2 | Dissemination strategy | M6 | R | PU | |
| D13.3 | Dissemination coordination platform | M6 | P | RE | |
| D13.4 | Plans for contribution to standardisation work | M12 | R | PU | |
| D13.5 | First draft of exploitation strategy Updated | M12 | R | CO | |
| D13.6 | Dissemination strategy | M18 | R | PU | |
| D13.7 | Intermediate Dissemination and feedback report | M18, M30 | R | PU | |
| D13.8 | Updated Exploitation Strategy | M21 | R | RE | |
| D13.9 | Report on projects connected to Hydra | M24 | R | PU | |
| D13.10 | Intermediate Standardisation Report | M28 | R | RE |
[1] Deliverable numbers in order of delivery dates: D1.1 – D13.10
[2] Month in which the deliverables will be available. Month 0 marking the start of the project, all delivery dates relative to start date.
[3] The nature of the deliverable using one of the following codes: R = Report - P = Prototype - D = Demonstrator - O = Other
[4] The dissemination level using one of the following codes: PU = Public PP = Restricted to other programme participants (including the Commission Services). RE = Restricted to a group specified by the consortium (including the Commission Services). CO = Confidential, only for members of the consortium (including the Commission Services).
Posted by Admin
on April 16 2010
64177 Reads ·
