Guidance to provider of telemedicine solutions and the third party supplier

The purpose of the application documentation is to serve as a guide for the third party who must prepare integrations to the Infrastructure as part of a telemedicine solution (i.e. a Vendor Application Provider), or new components for the Infrastructure. The documentation is used for teaching the use of the Infrastructure's system interface.

This guidance must be used by provider of telemedicine solution, or third party suppliers of components for the Infrastructure. The guidance is used for teaching the use of the Infrastructure's system interface.

This documentation must guide the use of all essential functions and the system interface.

The pages linked from this page will enable a user of the eHealth Infrastructure interface to use Telemedicine Infrastructure's system interfaces.

Architecture and Domains provides and introduction to the eHealth Infrastructure domain and services.
Requirements for developing on the eHealth Platform list the requirements for developing to the eHealth Infrastructure.
For designing Telemedicine Solutions are number of design guides are described here Best Practices and Design Guidelines
The API of the eHealth services are described here:
- Clinical Domain DK.EHEALTH.SUNDHED.FHIR.IG.CORE\Home - FHIR v4.0.1
- Administrative Domain DK.EHEALTH.SUNDHED.FHIR.IG.CORE\Home - FHIR v4.0.1
- SSL Domain Technical documentation of the Service, Support, and Logistics API for eHealth
The interaction with eHealth Services are described here:
- Clinical Domain Interacting with Services in the Clinical Domain
- Administrative Domain Interacting with Services in the Administrative Domain
- SSL Domain Technical documentation of the Service, Support, and Logistics API for eHealth
Security Mechanisms describes the requires authentication, and authorization for accessing the eHealth services.

The Frequently Asked Questions section contains some questions and answers for developing Telemedicine Solutions.