openhealth-list  

Messages by Thread

• • Re: URL_callable application interface, was Re: graph from patient data David Forslund
  • Re: URL_callable application interface, was Re: graph from patientdata Andrew Ho
  • Re: graph from patient data Andrew Ho
  • Re: graph from patient data David Forslund
  • Re: graph from patient data Karsten Hilbert
  • Re: graph from patient data David Forslund
  • RE: graph from patient data Tim Churches
  • Re: graph from patient data Horst Herb
  • Re: graph from patient data David Forslund
  • RE: graph from patient data Tim Churches
  • Re: graph from patient data Horst Herb
  • RE: graph from patient data Tim Churches
  • Re: graph from patient data Horst Herb
  • Re: graph from patient data Thomas Beale
  • physicians v technical people (was Re: graph from patient data) Thomas Beale
  • Re: graph from patient data Adrian Midgley
• IOM EMR david derauf
  • Re: IOM EMR Wayne Wilson
• Announcing GT.M V4.4-002 and V4.4-FT01 K.S. Bhaskar
• ADL - Archetype Definition Language Thomas Beale
• Switching to Open Source Software Tim Cook
• Delaware dramtic plans david derauf
  • Re: Delaware dramtic plans Richard Schilling
• Re: Open-source hospital level medical stock control system in SouthAfrica Etienne Saliez
  • Re: Open-source hospital level medical stock control system in SouthAfrica Willem van der Walt<[EMAIL PROTECTED]>
• "unsubscribe" jon hoeksma
• Announcement (WARNING: SAD) Brian Bray
  • Re: Announcement (WARNING: SAD) Andrew Ho
  • Re: Announcement (WARNING: SAD) Ignacio Valdes
  • Re: Announcement (WARNING: SAD) Richard Schilling
  • Re: Announcement (WARNING: SAD) Etienne Saliez
  • Re: Announcement (WARNING: SAD) Douglas Carnall
• Re: Open-source hospital level medical stock control system Tim Churches
  • OptoLight Re: Open-source hospital level medical stock controlsystem Tim Cook
  • RE: Open-source hospital level medical stock control system Beza, Fil
  • RE: Open-source hospital level medical stock control system Willem van der Walt<[EMAIL PROTECTED]>
  • Re: Open-source hospital level medical stock control system Tim Cook
• Re: FreeB:: Billing Item equality Karsten Hilbert
  • Re: FreeB:: Billing Item equality Fred Trotter
• TORCH Import Tim Cook
• Re: Re: OIO's data model (was RE: HHS announcement regarding Snomed) Tim Churches
• Re: Gratis vs Liberated Adrian Midgley
• Re: HHS announcement regarding Snomed Andrew Ho
  • OIO's data model (was RE: HHS announcement regarding Snomed) Tim Churches
  • Re: OIO's data model (was RE: HHS announcement regarding Snomed) Andrew Ho
  • Re: OIO's data model (was RE: HHS announcement regarding Snomed) Tim Cook
  • TORCH's data model, was Re: OIO's data model (was RE: HHS announcementregarding Snomed) Andrew Ho
  • Re: TORCH's data model, was Re: OIO's data model (was RE: HHSannouncement regarding Snomed) Tim Cook
  • Re: TORCH's data model, was Re: OIO's data model (was RE: HHSannouncement regarding Snomed) Andrew Ho
  • Re: HHS announcement regarding Snomed David Forslund
  • OpenEMed to use SNOMED, Re: HHS announcement regarding Snomed aho
  • Re: OpenEMed to use SNOMED, Re: HHS announcement regarding Snomed David Forslund
  • Re: OpenEMed to use SNOMED, Re: HHS announcement regarding Snomed Richard Schilling
  • Re: HHS announcement regarding Snomed Adrian Midgley
  • SNOMED CT in U.K., was Re: HHS announcement regarding Snomed Andrew Ho
  • Re: SNOMED CT in U.K., was Re: HHS announcement regarding Snomed Adrian Midgley
  • Re: SNOMED CT in U.K., was Re: HHS announcement regarding Snomed Andrew Ho
  • Re: SNOMED CT in U.K., was Re: HHS announcement regarding Snomed Adrian Midgley
• guidelines for taxpayer funded software Horst Herb
  • Re: guidelines for taxpayer funded software Karsten Hilbert
  • Re: guidelines for taxpayer funded software Sujai \"Ron\" Nath
  • Re: guidelines for taxpayer funded software Tim Churches
• European patents and open source Tim Churches
• [Fwd: Billing issues] Fred Trotter
• Fwd: CALL FOR 150 DEVELOPERS/SYSTEM ANALYSTS/PROJECT MANAGERS. Great opportunity for Open Source development! [[email protected]] Richard Schilling
  • Re: Fwd: CALL FOR 150 DEVELOPERS/SYSTEM ANALYSTS/PROJECT MANAGERS. Great opportunity for Open Source development! [[email protected]] Tim Churches
  • Re: Fwd: CALL FOR 150 DEVELOPERS/SYSTEM ANALYSTS/PROJECT MANAGERS. Great opportunity for Open Source development! [[email protected]] Richard Schilling
  • CALL FOR 150 DEVELOPERS/etc Douglas Carnall
  • Re: CALL FOR 150 DEVELOPERS/etc Richard Schilling
• Billing logging, legal issues Fred Trotter
• Re: [Fwd: [torch] views on "clean demo" site] Pat
  • Re: [Fwd: [torch] views on "clean demo" site] Fred Trotter
  • Re: [Fwd: [torch] views on "clean demo" site] Pat
  • Re: [Fwd: [torch] views on "clean demo" site] Karsten Hilbert
  • Re: [Fwd: [torch] views on "clean demo" site] Karsten Hilbert
  • Re: [Fwd: [torch] views on "clean demo" site] Tim Churches
  • Re: [Fwd: [torch] views on "clean demo" site] Karsten Hilbert
  • Re: [Fwd: [torch] views on "clean demo" site] Pat
• Re: telemedicine via satellite Richard Schilling
  • Re: telemedicine via satellite Jel Coward
• Richard Stallman sheds light on SCO vs. Free Software Andrew Ho
  • Re: Richard Stallman sheds light on SCO vs. Free Software Adrian Midgley
  • "Free software" misleads? was Re: Richard Stallman sheds light onSCO vs. Free Software Andrew Ho
• 3rd HL7 Australia Conference on Decision Support Standards open for registration Klaus Veil
• question re current EHR/data submit software Heitzso
  • Re: question re current EHR/data submit software Karsten Hilbert
  • Re: question re current EHR/data submit software Andrew Ho
  • Re: question re current EHR/data submit software Karsten Hilbert
• RE: Keyword tagging of clinical documents Joseph Dal Molin
  • Re: Keyword tagging of clinical documents Dr. David H Chan
  • RE: Keyword tagging of clinical documents Tim Churches
  • RE: Keyword tagging of clinical documents Kantor, Gary
• Re: Evaluating EHR - Billing Problem, EMR problem Falball
• Re: Clinical Trial Management System Calle Hedberg
• Something useful for the FreeBill project Smith, Todd
• Re: Evaluating EHR Falball
  • Re: Evaluating EHR - Billing Problem, EMR problem Fred Trotter
  • Re: Evaluating EHR Adrian Midgley
  • Re: Evaluating EHR Tim Cook
• Thompson blasts state of health care IT david derauf
• Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Horst Herb
• Tim Churches Andrew Ho
  • IMPORTANT RE PERSONAL ATTACKS Dave Scott
• Re: EHR on a stick, Re: Federated or Consolidated EHR was: relationaldatabases may not be the right tool for medical records Thomas Beale
• Re: alternatives to OIO, was RE: evaluating EHR, Daniel L. Johnson
• Re: Question was RE: Federated or Consolidated EHR was: relationa l da tabases may not be the right tool for medical records (fwd) Adrian Midgley
• FreeMED Billing .02 alpha release Fred Trotter
  • Re: FreeMED Billing .02 alpha release David Forslund
  • Re: FreeMED Billing .02 alpha release Fred Trotter
  • Re: FreeMED Billing .02 alpha release David Forslund
  • Re: FreeMED Billing .02 alpha release Ron Fox
  • Re: FreeMED Billing .02 alpha release John Gage
  • Re: FreeMED Billing .02 alpha release John Gage
  • Re: FreeMED Billing .02 alpha release Ron Fox
  • Re: FreeMED Billing .02 alpha release Thomas Beale
• The evils of software patents - 2nd try Tim Churches
  • Re: Re: The evils of software patents - 2nd try Richard Schilling
  • Re: Re: The evils of software patents - 2nd try Tim Churches
• The evils of software patents Tim Churches
  • RE: The evils of software patents Smith, Todd
  • RE: The evils of software patents richard clark
  • Re: The evils of software patents Adrian Midgley
  • Re: The evils of software patents Tim Churches
• Question was RE: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Shaw, Nikki
  • ... Scripting in existing systems: novel outputs etc [was: ....] Adrian Midgley
• RE: GT.M as OODBMB was: Re: Federated or Consolidated EHR was: relational databases may n ot be the right tool for medical records Smith, Todd
  • Re: GT.M as OODBMB was: Re: Federated or Consolidated EHR was: re lational databases may n ot be the right tool for medical records Richard Schilling
• Re: Some GT.M thoughts was RE: Federated Richard Schilling
• Java interface to GT.M was: Re: Federated or Consolidated EHR was: relational databases may n ot be the right tool for medical records Richard Schilling
  • Re: Java interface to GT.M was: Re: Federated or Consolidated EHRwas: relational databases may n ot be the right tool for medical records Tim Churches
  • Re: Java interface to GT.M was: Re: Federated or Consolidated EHR was: relational databases may n ot be the right tool for medical records David Forslund
  • Re: Java interface to GT.M was: Re: Federated or Consolidated EHR was: relational databases may n ot be the right tool for medical records Richard Schilling
  • RE: Java interface to GT.M was: Re: Federated or Consolidated EHR was: relational databases may n ot be the right tool for medical records Smith, Todd
• Re: relational databases may not be the right tool for medical records David Forslund
• Re: Federated or Consolidated EHR was: relational databases may notbe the right tool for medical records Tim Churches
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records David Forslund
  • Re: Federated or Consolidated EHR was: relational databases may notbe the right tool for medical records Tim Churches
  • Re: Federated or Consolidated EHR was: relational databases maynot be the right tool for medical records Tim Cook
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records David Forslund
  • Re: Federated or Consolidated EHR was: Fred Trotter
  • Re: Federated or Consolidated EHR was: David Forslund
  • Re: Federated or Consolidated EHR was: Tim Cook
  • Re: Federated or Consolidated EHR was: Tim Cook
  • Re: Federated or Consolidated EHR was: Tim Churches
  • Re: Federated or Consolidated EHR was: Tim Cook
  • Standards and Interoperability (was federation...) David Forslund
  • Re: Federated or Consolidated EHR was: Daniel L. Johnson
  • Re: Federated or Consolidated EHR was: relational databases may notbe the right tool for medical records Tim Churches
• Re: Federated or Consolidated EHR was: relational databases maynot be the right tool for medical records Tim Cook
  • Re: Federated or Consolidated EHR was: relational databases may notbe the right tool for medical records Tim Churches
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Richard Schilling
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Adrian Midgley
  • Re: Federated or Consolidated EHR was: relational databases maynot be the right tool for medical records Tim Cook
  • Re: Federated or Consolidated EHR was: relational databases maynot be the right tool for medical records Tim Cook
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records David Forslund
  • Re: Federated or Consolidated EHR was: relational databases maynot be the right tool for medical records Tim Cook
  • Re: Federated or Consolidated EHR was: relational databases maynot be the right tool for medical records Tim Cook
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Richard Schilling
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records [[email protected]] Richard Schilling
  • Re: portable electronic record size Richard Schilling
  • Re: portable electronic record size Michael D. Weisner
  • Re: portable electronic record size Daniel L. Johnson
  • Re: EHR on a stick, Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Karsten Hilbert
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records Karsten Hilbert
  • Re: Federated or Consolidated EHR Fred Trotter
  • Re: Federated or Consolidated EHR was: relational databases may not be the right tool for medical records David Forslund
• VistA use: research question Daniel L. Johnson
  • Re: VistA use: research question Wayne Wilson
  • Shared EMR data initiative david derauf
• RE: Bring your laptops/PCs to the Sacramento meeting Pat
  • RE: Bring your laptops/PCs to the Sacramento meeting Andrew Ho
• For what it's worth dept.: SCO vs the World Daniel L. Johnson
• Re: Perl or Python (was instantiated in Billing) Karsten Hilbert
• FreeMED Status #1 Fred Trotter
  • Re: FreeMED Status #1 Karsten Hilbert
  • Re: FreeMED Status #1 Adrian Midgley
• Re: FreeMED Billing Project Karsten Hilbert
  • Re: FreeMED Billing Project Fred Trotter
  • Re: FreeMED Billing Project Adrian Midgley
  • Re: FreeMED Billing Project Alexander Caldwell
  • Re: FreeMED Billing Project Karsten Hilbert
  • Re: FreeMED Billing Project Karsten Hilbert
  • Re: FreeMED Billing Project Fred Trotter
• On Jabber as a User only... Fred Trotter
  • Re: On Jabber as a User only... Karsten Hilbert
  • Re: On Jabber as a User only... Fred Trotter
  • Re: On Jabber as a User only... Karsten Hilbert
  • Re: On Jabber as a User only... Fred Trotter
• Draft of paper about Debian-Med Andreas Tille
• Open Source adoption research in health care Obal and Jin
  • Re: Open Source adoption research in health care Horst Herb
  • Re: Open Source adoption research in health care Joseph Dal Molin
  • Re: Open Source adoption research in health care Ignacio Valdes
• press coverage of developments from OSHCA 2 Adrian Midgley
• Draft Essay on OS Mgt... Daniel L. Johnson
• Re: AAFP EHR project Andrew Ho
  • Re: AAFP EHR project Adrian Midgley
• AAFP EHR project summary Daniel L. Johnson
  • Re: AAFP EHR project summary Karsten Hilbert
  • Re: AAFP EHR project summary Andrew Ho

[Earlier messages] [Later messages]