Delivery-Date: Mon, 30 May 2016 20:20:04 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [138.201.14.202])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id E82E71E0AF1;
	Mon, 30 May 2016 20:20:01 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 06744E0D5F;
	Tue, 31 May 2016 00:19:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 578B8E0D26
 for <tor-talk@lists.torproject.org>; Tue, 31 May 2016 00:19:53 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id aUFtIQnQeqDx for <tor-talk@lists.torproject.org>;
 Tue, 31 May 2016 00:19:53 +0000 (UTC)
Received: from srv-ch-mail.apawc.com.au (203-206-175-55.perm.iinet.net.au
 [203.206.175.55])
 by eugeni.torproject.org (Postfix) with ESMTP id BD566E0CB6
 for <tor-talk@lists.torproject.org>; Tue, 31 May 2016 00:19:52 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by srv-ch-mail.apawc.com.au (Postfix) with ESMTP id 75090AA810E
 for <tor-talk@lists.torproject.org>; Mon, 30 May 2016 20:19:49 -0400 (EDT)
Received: from srv-ch-mail.apawc.com.au ([127.0.0.1])
 by localhost (srv-ch-mail.apawc.com.au [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id qY0ZadduFfcg for <tor-talk@lists.torproject.org>;
 Mon, 30 May 2016 20:19:48 -0400 (EDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
 by srv-ch-mail.apawc.com.au (Postfix) with ESMTP id DD44AAA825B
 for <tor-talk@lists.torproject.org>; Mon, 30 May 2016 20:19:48 -0400 (EDT)
X-Virus-Scanned: amavisd-new at apawc.com.au
Received: from srv-ch-mail.apawc.com.au ([127.0.0.1])
 by localhost (srv-ch-mail.apawc.com.au [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id yfgtAaWiMaXI for <tor-talk@lists.torproject.org>;
 Mon, 30 May 2016 20:19:48 -0400 (EDT)
Received: from srv-ch-mail.apawc.com.au (srv-ch-mail.apawc.com.au
 [192.168.0.16])
 by srv-ch-mail.apawc.com.au (Postfix) with ESMTP id C403EAA810E
 for <tor-talk@lists.torproject.org>; Mon, 30 May 2016 20:19:48 -0400 (EDT)
Date: Tue, 31 May 2016 00:19:48 +0000 (UTC)
From: Paul Templeton <paul@apawc.com.au>
To: tor-talk@lists.torproject.org
Message-ID: <1539309998.31648.1464653988743.JavaMail.zimbra@apawc.com.au>
In-Reply-To: <1702871614.31614.1464651525212.JavaMail.zimbra@apawc.com.au>
MIME-Version: 1.0
X-Originating-IP: [115.186.227.198]
X-Mailer: Zimbra 8.0.4_GA_5737 (ZimbraWebClient - FF44 (Win)/8.0.4_GA_5737)
Thread-Topic: Could Tor be used for health informatics?
Thread-Index: 5eYcXJJXxZ7Dy5KUgj78j96eptB5pw==
Subject: [tor-talk] Could Tor be used for health informatics?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

I've been toying with an idea for several years now to facilitate data exchange between health services/providers. Over the last 10 years or so here in Australia the government has funded many projects to allow secure messaging between providers. The majority of projects flopped but one stuck. There are now two players in the market both are now corporate entities (Even though one was a NGO with FOSS application).

One system (HealthLink) is a push pull system that(I believe) stores the data in New Zealand. This is initiated from the poster (ie sending discharge or report).

The second is Argus - it just uses SMTP to send data.

The Government is now in its last bid to force all Australian to have electronic health records(My Health Record). It was an opt in system but the public didn't trust the Government so now its an opt out.

I have been involved from the early days of trying to get some sort of secure data exchange that is controlled by the consumer. I have many a time stated the best approach would be a secure, encrypted peer to peer system to push and pull data at the request of the consumer. Even though many Government Departments involved thought the idea was good they didn't know how to implement plus I think the mandate was more about the Government having access to personal data. 

Where Tor may fit...

The Tor network would provide the secure transport - each site would create an onion address. Central servers would keep tab of address and public keys for each site and practitioner. (down side of the current key infrastructure is the Government creates the key pair and keeps a copy, I would suggest the practitioners create there own keys). The system would use HL7 for data exchange. An app on the practitioners sever would then interpret the requests and talk to the SQL DB. 

The Practitioners DB would have to be modified for permissions to access data based on the customers request. Most DBs all ready have logic fields for consent on many aspects of the clinical data - ie consent for data to be used for chronic disease research, SMS reminders etc.

The only area I fail is the ability for a customer to access there record to set permissions...

Any thoughts out there?

Regards,

Paul Templeton
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

