| Excerpt |
|---|
The purpose of the application documentation is to serve as a guide for a third party preparing integration to the Infrastructure as part of a telemedicine solution (as a Vendor Application Provider) and as a guide for the supplier of new component(s) for the Infrastructure. The documentation is used for teaching the use of the eHealth Infrastructure system interface. |
...
must be used by providers of telemedicine solutions and third-party suppliers of components for the eHealth Infrastructure.
guides the use of all essential eHealth Infrastructure functions and the system interface.
is used for teaching the use of the eHealth Infrastructure system interface.
...
Architecture and Domains provides an introduction to the eHealth Infrastructure domains and services.
Technical Requirements for developing on the eHealth PlatformDeveloping Telemedicine Solutions lists the requirements for developing to the eHealth Infrastructure.
A number of design guides for designing Telemedicine Solutions are described at Best Practices and Design Guidelines.
The APIs of the eHealth Infrastructure 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
Service, Support & Logistics (SSL) Domain Technical documentation of the Service, Support, and Logistics API for eHealth
The interaction with eHealth Infrastructure services are is 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 authentication, authorization, federation and access control performed in eHealth services.
Development and deployment cycle describes tools for development and integration into the eHealth Infrastructure deployment model.
...