...
An HTTPS connection is mandatory.
We will provide you with a username/password for (HTTPS) authentication linked to your PKB Organisation.
For our production server, we will need to know what IP address(es) you will be connecting from. We use this in 2 ways:
We will whitelist it at the firewall level
When an HL7 message is received, the incoming IP is checked against a specific whitelist for your PKB Organisation. If this check fails, the message will be rejected with a generic message.
We do not enforce IP whitelisting in our test environments.
Messages for patients for whom you do not have decryption access a consent record (e.g. those outside of your PKB Organisation) will still be accepted.
Configuration
...
Aliases are not case sensitive.
PKB Aliasing Checklist:
Agree on alias values to send in MSH-4 in sandbox. Client
Create teams (that align to aliases from step 1) in Sandbox. Client + PKB
Assign coordinators and any other requested users for teams. Client + PKB
Configure interface to always send one of the alias values from step 1. Client
Configure org and/or team alias options from admin GUI. PKB
Run UAT in sandbox. Client
Agree on alias values to send in MSH-4 in production. Client
Create teams (that align to aliases from step 7) in production. Client + PKB
Assign coordinators and any other requested users for teams. Client + PKB
Configure interface to always send one of the alias values from step 7. Client
Configure org and/or team alias options from admin GUI. PKB
Monitor interfaces to ensure no rejections due to aliases.