Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Provides questions and answers for developing Telemedicine Solutions for the eHealth Infrastructure.

FHIR

Development and deployment lifecycle

  • Development and deployment lifecycle

    • Question: Where do I find a description of responsibilities and workflow to on how to deploy a new application on the infrastructure.

    • Answer: See Development and deployment cycle.

    • Question: Docker basic images are available from eHealth DK's docker registry. How are these accessed (username and password are required)?

    • Answer: To get access you need to be registered as a supplier. Contact FUT-S. See Contact Information.

    • Question: The documentation states that images must be signed with a private key, and that the public key must be sent. How is the public key sendt?

    • Answer: Contact FUT-S. See Contact Information.

    • Question: It is described that the application or services shall be deployed in the eHealth Infrastructure with an official eHealth helm chart. It is unclear whether it is the the Telemedicine Solution provider who shall create the helm chart or whether this is the eHealth infrastructure owner's task?

    • Answer: It is the Telemedicine Solution provider task to create the helm chart.

    • Question: Helmsman config is mentioned in Development and deployment cycle . It is unclear whether this is something the supplier needs to deal with, or whether this is platform owner documentation for deploying applications?

    • Answer: It is the Telemedicine Solution provider task to configure Helmsman.

  • No labels