Title

First AUTHORa, and Second AUTHOR b

a Affiliation

b Affiliation

Abstract. Abstract goes here. (MAX 300 Words)

Keywords. Keyword, keyword, keyword, keyword, keyword (4-8 Keywords. If applicable, please use MeSH_Terms: https://www.ncbi.nlm.nih.gov/mesh/ )

Introduction

Background

Please comply strictly with the instruction for the author and format specifications. We only accept camera ready word files (*.doc / *.docx). The article may not be longer than 8 pages. If the manuscript is longer than 6 pages a publication fee will be charged (7 pages = € 50, 8 pages = € 100).

If applicable, please use the reporting standards of the Equator Network (http://www.equator-network.org/ ) for the structure of the contribution. For evaluation papers please use the “STARE-HI--Statement on reporting of evaluation studies in Health Informatics.” (http://dx.doi.org/10.3414/ME10-01-0072 ). (in that case, please use the other template). These reporting standards following the IMRD-scheme (Introduction – Methods – Results – Discussion).

This fits not for technical concepts or technical case reports or reporting about standardization without evaluation. If applicable, please use for this kind of paper the ISCIL Scheme (Introduction – State of the art – Concept – Implementation – Lessons learned). This template is for manuscripts following the ISCIL-Schema, for all other reportings please use the other template.

In the section “1.1. Background” a short introduction into the general topic and the general problem should be given. What should be improved by this project or system?

Requirements

What requirements should be met in the project or by the software system? The focus should be on the requirements that are addressed in the manuscript.

State of the art

Please give an overview of the state of the art, related work and the short comings of existing solutions. This section should answer the question: “Why is a new concept necessary?”

Concept

This should include a description of the overall architecture of system. Details of any critical issues and how they were should be addressed and this approach should be compared with other options. The decisions should be explained.

Implementation

Describe your implementation and experience with the chosen approach. This can include screen-shots of the user interface or objectively verifiable facts, such as number of users, information about recorded or processed data.

Lessons learned (Discussion)

Have all the requirements of 1.2 been met? What can you learn from this project? What kind of support can be given for similar projects? Which concepts should you adopt, which ones should not?

Consider your approach to existing solutions: What are the innovations of this approach compared to the state of the art? What are the strengths and weaknesses of this approach compared to other approaches?

Note: The reviewers are encouraged to take a close look at this section. The focus will be set on the critical consideration of the chosen approach in comparison to other approaches and the degree of innovation.

Conclusion

What are the core statements of your approach?

Which are the most important lessons learned?

Conflict of Interest

Please indicate if one of the authors have an conflict of interest according to the principles of the ICJME. (http://icmje.org/conflicts-of-interest/ ) Otherwise indicate, “The authors state that they have no conflict of interests.”

References

Please strictly adhere to the specifications of IoS Press.

A.N. Author, Article title, Journal Title 66 (1993), 856–890.

Corresponding Author, Corresponding author, Book Department, IOS Press, Nieuwe Hemweg 6B, 1013 BG Amsterdam, The Netherlands; E-mail: bookproduction@iospress.nl.