Fw: [regrep] FW: Support for ebXML registry

["David RR Webber" <david@drrw.info>]

Team,

Here's is more info' on the NIST / Healthcare registry scenario.

DW.
----- Original Message ----- 
From: "Chiusano Joseph" <chiusano_joseph@bah.com>
To: "Robert Smik" <robert.smik@rainingdata.com>
Cc: "Boris Geller" <boris.geller@rainingdata.com>;
<regrep@lists.oasis-open.org>
Sent: Friday, February 27, 2004 1:55 PM
Subject: Re: [regrep] FW: Support for ebXML registry


> [Registry TC: More details on Raining Data and NIST - please let Robert
> Smik know if you have any more questions]
>
> Robert,
>
> Thank you for the technical overview you have provided below regarding
> TigerLogic's interaction with the NIST ebXML Registry.
>
> Joe
>
> Robert Smik wrote:
> >
> > Hi Joe
> >
> > For the HL7 demo TigerLogic was the sole VEHR (virtual electronic health
> > record repository) and
> > NIST was the registry.
> >
> > The goal was to register all incoming VEHR content with NIST for lookup
> > using RID query.
> > We have implemented NIST's HTTP registry interface to accomplish that
task.
> >
> > Upon receiving CDA and/or HL7 V3 messages, TigerLogic extracts header
> > information (metadata)
> > and registers it with along with a HTTP URL pointer back into TigerLogic
> > (for retrieval of the original document) with NIST. NIST indexes
provided
> > metadata and uses it to handle incoming lookup requests.
> >
> > Clients applications can access information either by direct query into
> > TigerLogic or by issuing a RID query to NIST. NIST is setup to do one of
the
> > following depending on the type of the request:
> > 1. return provided metadata with a pointer back into TigerLogic for the
> > original document
> > 2. return metadata only
> > 3. return actual document by performing a read from TigerLogic itself
> >
> > As a result of this integration, NIST will list TigerLogic as a partner
on
> > their web site.
> >
> > That's the overview. Please let me know if you have any
specific/technical
> > questions and I will address them.
> >
> > Regards,
> > Robert
> >
> > ----- Original Message -----
> > From: "Boris Geller" <boris.geller@rainingdata.com>
> > To: <chiusano_joseph@bah.com>
> > Cc: <boris.geller@rainingdata.com>; <Robert.smik@rainingdata.com>
> > Sent: Thursday, February 26, 2004 3:20 PM
> > Subject: Re: [regrep] FW: Support for ebXML registry
> >
> > >
> > > I thought he was, but just in case - here it is, again.
> > >
> > > Thanks, Joe.
> > >
> > > Boris.
> > >
> > >
> > > -----Original Message-----
> > > From: "Chiusano Joseph" <chiusano_joseph@bah.com>
> > > Date: Thu, 26 Feb 2004 16:55:34
> > > To:Boris Geller <boris.geller@rainingdata.com>
> > > Subject: Re: [regrep] FW: Support for ebXML registry
> > >
> > > Thanks Boris - I did not see Robert Smik on the CC list, unless he was
> > > bcc'd.
> > >
> > > Boris Geller wrote:
> > > >
> > > > Hi Joe,
> > > >
> > > > Great to hear from you.
> > > >
> > > > Yes, we've been working with NIST, HL7, IHE and several other
vendors
> > over the past few months to create an interoperabulity framework
consisting
> > of our TigerLogic XML repository and NIST ebXML registry. That's what
we've
> > been demonstrating at the HIMSS conference this week.
> > > >
> > > > As I undestand it, NIST took an open source implementation of the
> > registry and extended it to work better in various healthcare scenarios.
> > That's what we interoperate with in the HL7-IHE demo.
> > > >
> > > > I've CC'd Robert Smik at RDTA as well. Robert is the one that has
beed
> > working with his counterparts at NIST to implement this integration.
> > > >
> > > > Robert, please respond with a brief technical summary of what we've
been
> > able to accomplish for the demo with NIST.
> > > >
> > > > Joe, also, I'll be in DC next week and will be glad to get together
to
> > provide additional details.
> > > >
> > > > Regards,
> > > >
> > > > Boris.
> > > >
> > > > Mobile 415-601-2206
> > > >
> > > > VP, Market Development
> > > > Raining Data Corp.
> > > > Nasdaq: RDTA
> > > >
> > > > www.rainingdata.com
> > > >
> > > > -----Original Message-----
> > > > From: "Chiusano Joseph" <chiusano_joseph@bah.com>
> > > > Date: Thu, 26 Feb 2004 14:17:18
> > > > To:boris.geller@rainingdata.com
> > > > Cc:"Breininger Kathryn R" <kathryn.r.breininger@boeing.com>,
David
> > RR Webber - XML ebusiness <Gnosis_@compuserve.com>,
> > Monica.Martin@Sun.COM, Farrukh Najmi <farrukh.najmi@Sun.COM>,
Duane
> > Nickull <dnickull@adobe.com>, Alan Kotok <AlanKotok@cs.com>
> > > > Subject: Re: [regrep] FW: Support for ebXML registry
> > > >
> > > > [Including Boris Geller of Raining Data for more information on the
> > > > HIMSS press release]
> > > >
> > > > Boris,
> > > >
> > > > Hope all is well. I'm wearing my OASIS/ebXML Registry TC hat on this
> > > > e-mail, with several of my TC colleagues copied. Is there any
> > > > information you can provide us regarding the recent HIMSS press
release,
> > > > in reference to TigerLogic's support of NISTS's ebXML registry?
> > > > (pertinent quote is below)
> > > >
> > > > Thanks,
> > > > Joe
> > > >
> > > > PERTINENT QUOTE:
> > > >
> > > > Moreover, the TigerLogic XML Life Sciences Data Server delivers
built-in
> > > > support for healthcare delivery, lab testing, and data management
> > > > standards, including: HL7's Clinical Document Architecture (CDA) and
V3
> > > > XML lab messages; IHE's Retrieve Information for Display (RID)
query;
> > > > the Clinical Data Interchange Standards Consortium's (CDISC)
laboratory
> > > > (LAB), Operational Data Model (ODM), and Submissions Data Standard
(SDS)
> > > > specifications; and the National Institute of Standards and
Technology's
> > > > (NIST) ebXML healthcare registry, which could serve as a model for
> > > > providing access to distributed healthcare documents, making it
easier
> > > > to find patient records.
> > > >
> > > > "Breininger, Kathryn R" wrote:
> > > > >
> > > > > I am asking to have a section for 2.1 implementations added to our
> > > > > public home page, and links for the press release and demo cited
below
> > > > > posted there.  Any objections?
> > > > >
> > > > > Kathryn
> > > > >
> > > > > -----Original Message-----
> > > > > From: Carol Geyer [mailto:carol.geyer@oasis-open.org]
> > > > > Sent: Wednesday, February 25, 2004 11:41 AM
> > > > > To: Breininger, Kathryn R
> > > > > Subject: FW: Support for ebXML registry
> > > > >
> > > > >  fyi
> > > > > --carol
> > > > >
> > > > > -----Original Message-----
> > > > > From: AlanKotok@cs.com [mailto:AlanKotok@cs.com]
> > > > > Sent: Wednesday, February 25, 2004 1:22 PM
> > > > > To: david@drrw.info; carol.geyer@oasis-open.org;
> > Monica.Martin@Sun.COM;
> > > > > Farrukh.Najmi@Sun.COM
> > > > > Subject: Support for ebXML registry
> > > > >
> > > > > David, Carol, Monica, Farrukh:
> > > > >
> > > > > I saw a release on Monday coming out of the HIMSS (health care IT)
> > > > > conference about a demo involving and vendor support for ebXML
> > registry.
> > > > > The vendor is Raining Data, and its release is found at
> > > > > http://www.rainingdata.com/company/pressroom/himss.html . A
> > description
> > > > > of the demo, also from Raining Data, is found at
> > > > > http://www.rainingdata.com/products/tl/docs/tl_himss.pdf .  It
looks
> > > > > like the demo uses the NIST registry.
> > > > >
> > > > > Best regards.
> > > > >
> > > > > Alan Kotok
> > > > > AlanKotok@cs.com
> > > > > http://www.technewslit.com/
> > > > > Editor, ebXML Forum, http://www.ebxmlforum.org/ Editor,
> > > > > PublicDiplomacy.Org, http://www.publicdiplomacy.org/
> > > > >
> > > > > To unsubscribe from this mailing list (and be removed from the
roster
> > of the OASIS TC), go to
> >
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
> > >
> > >
>
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.
>
>