X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E078A9FA3B3 for ; Mon, 15 May 2006 12:08:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 93734-07-2 for ; Mon, 15 May 2006 12:08:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id D454B9FA4E1 for ; Mon, 15 May 2006 12:08:37 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Mon, 15 May 2006 15:08:34 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 15 May 2006 10:08:33 -0500 Subject: Re: Copy HL7 record/file into PostgreSQL Table From: Scott Marlowe To: "Jim C. Nasby" Cc: Sean Hamilton , "Kenneth B. Hill" , pgsql-admin@postgresql.org In-Reply-To: <20060515145954.GB26212@pervasive.com> References: <4464C26A.40300@chfund.org> <20060515145954.GB26212@pervasive.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1147705713.9755.127.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 15 May 2006 10:08:33 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/178 X-Sequence-Number: 21710 On Mon, 2006-05-15 at 09:59, Jim C. Nasby wrote: > On Fri, May 12, 2006 at 01:14:18PM -0400, Sean Hamilton wrote: > > I'm currently working on an EHR myself and would love to hear a solution > > to this.. If youget valuable feedback can you please forward that to me? > > and if I hear anything I'll do the same > > Given how complex HL7 apparently is (someone up-thread was estimating a > week to write a parser) you might want to go with more of a pre-canned > solution rather than trying to roll your own. The week I was estimating was for creating what appear to be all the ancillary tables listed in that spec, and testing to make sure you've got the schema all right. Just importing the data that was presented looked fairly easy. It was the validating it that looked hard... Just clarifying.