(Created page with "Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways: SFTP Pull SFTP Push HTTPS Post MLLP Send == SFTP...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways: | Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways: | ||
== SFTP Pull == | == SFTP Pull == | ||
Revision as of 17:16, 25 March 2020
Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:
SFTP Pull
GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.
SFTP Push
The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.
HTTPS Post
The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.
MLLP Send
Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.