Sign e-prescription

Installation of client

The locally installed erxproxy client ensures that no sensitive patient data leaves the organization of the signing physicians. The documentation contains alternative names for the client, for example CLI (command line interface) or proxy. Github Repository:

https://github.com/eprescription-ch/erxproxy

TIP

The client can also be run as a Docker container in an OpenShift environment. The image can be found at healthinfonetag/erxproxy

The erxproxy must be able to communicate with the core application and with the external API. It is recommended that the erxproxy be placed as close as possible to the core application.

Launching of client Test environment:

./erxproxy server --env test

Production environment (--env prod is the default):

./erxproxy server

Specifying a different port (e.g. 8086 instead of 8092) is done using the parameter port:

./erxproxy server --port 8086

Check access

It must be ensured that the following domains and endpoints are accessible and are not blocked by proxy settings or firewall rules:

Test Environment

https://oauth2.hin.ch/REST/v1/OAuth/GetAccessToken
https://oauth2.authservice-int.hin.ch/api
https://api.testnet.certifaction.io
https://api.erx.test.certifaction.io

Prod Environment

https://oauth2.hin.ch/REST/v1/OAuth/GetAccessToken
https://oauth2.authservice.hin.ch/api
https://api.certifaction.io
https://api.erx.certifaction.io