Before you begin integrating the eMed iframe into your website, please meet these prerequisites:
-
Origin whitelisting
Communicate to eMed the complete list of origins (i.e., the protocols, domains, and ports) from which you plan to load the iframes. This list should include the origins of your production environment and any test environments you will use during the development and testing phases. Whitelisting is necessary to enable your users’ browsers to load the iframes securely and without issues related to cross-origin resource sharing (CORS) policies.
-
Contract and appointment configuration setup with eMed
Before the technical integration can commence, eMed must have set up at least one “contract” specific to your organisation. This contract includes the configurations necessary for your users to book appointments. The contract setup is a critical step that involves defining the scope of services, appointment mediums, service types, availability, etc that align with your requirements.
-
RSA public key for ID token
Provide eMed with your identity provider’s RSA public key to enable us to validate the ID Token. See ID Token.