Site Tools


Scope, Goal, and Process

This page is part of the OpenTele3 architectural design efforts.

With the overall goal of enabling development of better and more efficient solutions for users the specific goal of the OpenTele3 efforts is to begin a revision of OpenTele that can provide even better support for:

  • Development and maintenance with multiple software suppliers working in parallel.
  • Increased reuse of components across different solutions.
  • Improved support for international standards and interfaces.

One of the main vehicles in fulfilling these goals is working towards restructuring and further modularisation of the OpenTele platform along with the overall aim of standardising communication, interfaces and content formats wherever it makes sense. One part of this is identifying interfaces with other (existing) healthcare it systems and correspondingly identifying where existing OpenTele functionality can meaningfully be replaced by interfaces to external components. Furthermore, the task at hand explores where it makes sense to share modules and components across different telemedical solutions.

We thus include the following tasks in the scope of the effort:

  • What are the core components of a telemedical solution like OpenTele?
  • What functionalities and components can meaningfully be externalized and shared with other health IT systems?
  • With a solution like OpenTele, what are the main principles and guidelines for:
    • The service infrastructure for the core components?
    • The communication standards and content formats for main components?
    • The communication standards and content formats involved in talking to surrounding health IT systems?

We aim to answer the above questions by:

  1. Outlining general and specific principles for component design and interaction
  2. Identifying a number of the key current and future components and how they interact and exchange information.

That is, principles, key services and components along with recommendations on standards for communication and content are meant to practically shape and guide the step-by-step process from current “as-is” architecture towards the future “to-be” architecture.


The process shaping the principles, candidate components and proposals for use of standards is rooted in a strong involvement of key stakeholders and their experiences, requirements and plans. Thus, leading up to the initial phrasing of the design the 4S work group invited all interested parties to participate and contribute to the OpenTele3 effort. As a result a number of public as well as private parties have been included in the process via a series of meetings between 4S representatives and individual stakeholders. For more on this see the page on input from stakeholders. This input has been paramount to forming the current proposal.

Apart from direct input from stakeholders the work draws on reference architectures from the Danish eHealth Authority and existing, related analysis and reports:

The following are unfortunately all in Danish.

opentele3/ot3_scope_goal_process.txt · Last modified: 2018/12/12 13:27 (external edit)