Developing on the eHealth Platform
- Frederik Mogensen (Unlicensed)
- John Schneider
- Jens Kristian Villadsen
- Thomas Borup (Unlicensed)
Audience: eHealth infrastructure architects and developers.
Technical Requirements for Developing Telemedicine Solutions
This page describes the rules for developing telemedicine solutions to be deployed on or use of the infrastructure.
Designing Telemedicine solutions
Examples of different application types that can be built using the eHealth infrastructure.
Best Practices and Design Guidelines
Catalogue of design guides and best practices for developing Telemetric solutions using the eHealth infrastructure.
- Telemedicine Solutions caching of information from the infrastructure — When working with the eHealth Infrastructure, performance considerations are important, and caching is an important mechanism for achieving better performance.
- Performance Considerations — A list of best practices and anti-patterns regarding performance considerations and issues in application design.
Development and deployment cycle
Description of the eHealth development and deployment cycle, including description of the use of eHealth environments and flow.
- Build and deployment tools — Example screenshots for the build and deployment tools.
Overview of Tools in eHealth infrastructure
This is an overview of tools in the eHealth infrastructure available for Infrastructure Development and Development of Telemedicine solutions.
Useful third-party tools in the eHealth Infrastructure
This page describes the third-party tools (e.g. Jeager, Docker Repository, Splunk) used e.g. log analysis and tracing.
- Using Splunk — Splunk can be used by application vendors to access and query logs. This is a short introduction and references to Splunk end user documentation.
Logging model
This page describes the logging model for developing eHealth services or Telemedicine solutions. The intended audience is architects and developers.
- Finding logs from the different environments — Describes how to find logs for the different eHealth environments.
Call Tracing
The eHealth infrastructure makes it possible to trace all actions across different services and components. This is implemented using Istio and OpenTracing with Jaeger. The Call Tracing applies to both Telemedicine Solutions (3rd party) and eHealth Services (Infrastructure Provider)
Docker Base Images
Docker Base Images are the images that all applications running on the Infrastructure must build.
Canary deployment
Application Metrics
Application and services can expose application metrics in Prometheus format and have the metrics collected by the infrastructure.
URLs to access eHealth services
This page describes the URLs application vendors shall use to access eHealth infrastructure services.
Helm Charts
A helm chart is needed for installing an application on the eHealth Platform in a docker container ( https://helm.sh/docs/developing_charts/ https://helm.sh/docs/developing_charts/ ).
- Helm Chart - ehealth-job — This is the default helm chart for all jobs running on the eHealth platform.
- Helm Chart - ehealth-service — The default helm chart for all services running on the eHealth-platform. This is both platform services, eHealth services, and Telemedicine Solutions from third party.