Care Data Systems background and alternative ways we can play if theyhelp

[Jon Farmer <jfarmer@ic.net>]

Hello all,
I am Jon Farmer of Care Data Systems (www.caredatasystems.com) - regular
participant in HL7 demos.  Liora A. has brought you to my attention and I
would like to participate in ebXML demos.   We make tools for large-scale
consumer-centric systems integration, and we hope to discover and enhance
their usefulness in the ebXML environment.

We are prepared to do any of the following for the upcoming (Vienna) demo.
We defer to the planners to figure out how we can best help:

Functional capabilities:
- emit HL7 V3 XML registrations, orders, results, using DTDs and data from
February's HIMSS HL7 demo.
- participate as a repository, receiving all the healthcare data above plus
CDA documents, and provide for viewing of patient noteboook on Web (applet)
showing all content recieved from all sources.

Protocol Issues:
- We can participate either as a supplier of payload data to a role-player,
OR we can play the role directly, assuming the SOAP envelope is just
straighforward XML encapsulation and the header values are pretty static.
- We can communicate by any format over TCP/IP, including http, ftp, or
straight sockets.

Locations:
Our server is locate in Ann Arbor Michigan USA.
We would not be present in Vienna, but if "the Internet is up" we'll be
there "logically".
We would supply the URL of our downloadable (consumer notebook) applet.

For later demos there are numerous roles that look interesting and doable,
but the first time around we wanted to keep it pretty simple.

I have included a product overview as an addendum below for any who care for
the details at this point.

My contact info:
Jon Farmer
jfarmer@ic.net
734 856-8181 desk
734 856-9152 fax
734 652 4210 cell

My technical associate that will actually do our configuration is:
Martin Rose
mfrose@provide.net
734 647 8178 desk

Regards
Jon

====== PS: Care Data product line info =======================
Correlation Channel (CC) - real-time unattended identifer assignment and
cross-referencing.  Useful when participants are not using consistent
customer IDs (converts them all to master IDs or destination IDs on the
fly).

Integration Channel (IC) - transforms SQL, XML, CICS, DCOM, CORBA, and
Internet protocols.  Can expose a query object that delegates the query to
multiple systems and materializes the results.  Turns any person-data
streams into CC calls and repository updates.  Internet-based java Monitor

Access Channel (AC) - configurable person notebooks delivered by Applet or
Servlet.  Also provides search-and-register capability.

Secure Query Service (SQS) - provides interactive configuration of CORBA or
SQL queries, filtering result sets according to installable privacy policy
evaluators.

Extensible Person Data Repository (EPDR) - bundles all the above for a
zero-coding fed-by-anything internet-based enterprise data repository.

Our Customers are those with massive populations to integrate, but without
human intervention to map identifiers and without conventional programming
to transform traffic.

Jon
----- Original Message -----
From: Jon Farmer <jfarmer@ic.net>
To: <ebxml-poc@lists.ebxml.org>; <saskary@netfish.com>;
<swhandel@us.ibm.com>; <william.cox@bea.com>; <pdesmedt@viquity.com>
Cc: Martin Rose <mfrose@provide.net>
Sent: Monday, April 09, 2001 8:39 PM
Subject: Fw: ebXML PoC -- scenarios, roles, capabilities, etc.


> Hi all,
> I am Jon Farmer or Care Data Systems, regular participant in HL7 demos.
> Liora A. has brought you to my attention and I would like to participate
in
> ebXML demos.  For the upcoming (Vienna) demo we would like to take an easy
> role - supplying "payload-only" data for the following:
>
> hospital - emit HL7 V3 XML patient registrations
> laboratory - emit HL7 V3 XML lab orders or results
> These messages would be defined according to DTDs from Feb's HIMSS HL7
demo.
>
> We would emit them from our integration engine on an Internet-based server
> in Ann Arbor Michigan USA.  We would not be present in Vienna, but if "the
> Internet is up" we'll be there "logically".
>
> For later demos there are numerous roles that look interesting and doable,
> but on short notice we wanted to keep it extremely simple.
>
> My contact info:
> Jon Farmer
> jfarmer@ic.net
> 734 856-8181 desk
> 734 856-9152 fax
> 734 652 4210 cell
>
> My technical associate that will actually do our configuration is:
> Martin Rose
> mfrose@provide.net
> 734 647 8178 desk
>
>
> Please add us to your list so we can participate on calls.
> thanks
> Jon
>
> (PS Martin please capture the address list)
>
> > >To make sure this happens, we have set the following deadlines:
> > >- participants provide the information requested below, by
> close-of-business
> > >Friday, April 6;
>
> > >Please provide the following information (and feel free to add other
> > >categories if necessary):
> > >
> > >*       what are the scenarios that you can participate in? (refer to
PoC
> > >document for what the scenarios are)
> > >*       within these scenarios what is (are) the role(s) that you can
> play?:
> > >*       buyer
> > >*       supplier
> > >*       credit authority
> > >*       bank
> > >*       exchange
> > >*       laboratory
> > >*       hospital
> > >*       clinical data repository
> > >*       physician office
> > >*       registry provider
> > >*       registry client
> > >*       hub
> > >*       certificate authority
> > >*       provider of runtime codes
> > >*       other
> > >*       what functional capabilities can you provide? (based on Sig's
> > >Functional Requirements section):
> > >*       discovery from registry: CPP, business documents, core
components
> > >*       CPA formation
> > >*       dynamic trading configuration based on CPA
> > >*       execute business process for negotiation of CPA
> > >*       registry coordination with UDDI
> > >*       multi-hop messaging
> > >*       reliable messaging
> > >*       messaging security:
> > >*       DSIG for authentication
> > >*       PGP, S/MIME for encryption
> > >*       ability to access certificate authority
> > >*       secure access to registry contents
> > >*       HTTP messaging
> > >*       SMTP messaging
> > >*       trading based on defined business processes
> > >*       payloads
> > >*       participant will define payloads (DTD/Schema plus examples;
> specify
> > >source (OAG, RosettaNet, HL7, etc., or homegrown)
> > >*       participant defines payloads based on core components
> > >*       storage of core components in registry/repository
> > >*       business process capabilities
> > >*       storage in registry/repository
> > >*       business process editor
> > >*       CPA rendering through business process editor
> > >*       monitoring
> > >*       choreography expressed in ebXML Schema
> > >
> > >Based on the information that you provide, we'll do our best to come up
> with
> > >a fair allocation. Participants may or may not be able to show all of
> their
> > >capabilities at the PoC, based on time constraints, etc., but we'll do
> our
> > >best.
> > >
> > >Please send information to Sid (saskary@netfish.com), Sig
> > >(swhandel@us.ibm.com), Bill (william.cox@bea.com) and myself
> > >(pdesmedt@viquity.com). Feel free to include the entire PoC list if
> desired.
> > >
> > >Thanks. Again, please get this information in by Friday, April 6.
> > >
> > >-Philippe
> > >_______________________________
> > >Philippe De Smedt
> > >Architect
> > >Viquity Corporation (www.viquity.com)
> > >1161 N. Fair Oaks Avenue
> > >Sunnyvale, CA 94089-2102
> > >(408) 548-9722
> > >(408) 747-5586 (fax)
> > >pdesmedt@viquity.com
> > >
> > >
> > >------------------------------------------------------------------
> > >To unsubscribe from this elist send a message with the single word
> > >"unsubscribe" in the body to: ebxml-poc-request@lists.ebxml.org
> >
> >
>