W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > June 2010

HCLS Terminology conference call is scheduled for MONDAY, May 3, 2010

From: John Madden <john.madden@duke.edu>
Date: Sun, 13 Jun 2010 16:29:50 -0400
Cc: w3c semweb HCLS <public-semweb-lifesci@w3.org>
Message-Id: <8D61FB85-F539-453A-86F7-439FD4AFA5CE@duke.edu>
To: John Madden <john.madden@duke.edu>
This is a reminder that the next HCLS Terminology conference call  is 
scheduled for MONDAY, June 13, 2010. 

Conference Details 
      . Date of Call: Monday June 13, 2010 
      . Time of Call: 1600h UTC (1200h U.S. Eastern Daylight Time, 1700h 
London, 1800h CET, 0900h U.S. Pacific Standard Time) 
      . Dial-In #: +1.617.761.6200 (Cambridge, MA) 
      . Dial-In #: + (Nice, France) 
      . Dial-In #: +44.117.370.6152 (Bristol, UK) 
      . Participant Access Code: 42572# ("HCLS2") 
      . IRC Channel: irc.w3.org port 6665 channel #hcls2 
(see W3C IRC page for details, or see Web IRC*) 
      . Duration: ~1 hour 
      . Convener: John Madden 
      * Scribe: TBD 

Agenda: I would like to think more about how we could build part of an EHR
demo with our (and other) data. I especially like the HHS CAPRIT
scenario (discrepancies between radiology and pathology report to know
if the biopsy got it).

I (John M) may be called away, but let's give it a try.

* If you do not have an IRC client installed on your computer, you can get 
one of the many free one (search "irc client" and your platform), or you can 
use a web-based client. 

One possible web-based client you might try is Mibbit 
(http://www.mibbit.com/chat/). If you use mibbit, fill out the blanks like 
this (you need to click on "Server" to reveal the "Server address" field. 
Fill in server address with irc.w3.org:80. Select a chat name you like, 
often people use first name in lowercase followed by family name initial (no 
spaces, e.g. John Smith might use johnS). 

(Note that I suggest using port 80 from mibbit. The W3C irc server supports 
this, and it bypasses enterprise firewall issues that many users seem to be 
having with port 6667.) 

Received on Sunday, 13 June 2010 20:30:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:20:50 UTC