Re: [Gnumed-devel] lab data fetcher/importer connection methods

[Ian Haywood]

J Busser wrote:

>  > MediNet's Visual Basic (MS) desktop client
>  > - optionally runs in unattended mode
>  > - is configured by Medinet to hold the account id(s) for the
>  > mailbox(es) [directories] that are to be queried
>  > - runs an interactive session via ssh
Fair enough.
>  > - ssh connects to MediNet "frontend" server (outside firewall)
>  > - client (??) "calls"(??)
How?

>  >
>  > Manual customer-initiated sftp connections would be a confidentiality
>  > problem because sftp daemons are (apparently) not very good about
>  > restricting navigation across directories. Userid/pw credentials are
>  > not mapped/mappable to individual mailbox directory levels, ergo if a
>  > person connected *manually* there would be nothing to stop them
>  > browsing other directories
There relying on their remote client to restrict itself to the correct 
directories?
That's insane.
Remind me never to have HIV/hepC serology done in Canada ;-)
>  >
>  > **Could potentially do it in the other direction**
>  > Customer runs an sftp daemon on customer side
>  > Customer establishes SSH connection?
Sorry Jim this still isn't making any sense.
Either you are the server or the client, not both.

>  > MediNet script pushes the file over
>  >
>  >
>  > Data formats
>  >
>  > The data from *some* labs is coded within HL7 formatted files,
                                               ^^^^^^^^^^^^^^
We need samples to understand the dialect of HL7.
>  > permitting such data to be brought into patients' EMR as granular
>  > (individual coded test) results. However much of the lab data and
>  > reports handled by MediNet are plain text around which Medinet wraps
>  > a standard text header to permit vendors to link within their EMRs to
       ^^^^^^^^^^^^^^^
We need a description of this format and a few examples.
>  > individual patients, the data being imported as a document (text
>  > blob) rather than as coded values.

Ian

signature.asc
Description: OpenPGP digital signature