Emanuel,
The instructions for unsubscribing to this listserve are always included at
the end of each message. You should follow those instructions.
Rachel
-----Original Message-----
From: Emanuel Koseos [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 01, 2000 6:32 PM
To: Jonathan Borden; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: XML Schemas/DTD for HealthCare Industry
I have been trying to get off this e-mail list for the longest time - if you
could please remove me I would greatly appreciate it: [EMAIL PROTECTED]
and [EMAIL PROTECTED]
Regards,
Emanuel Koseos
Kaph Data Engineering
----- Original Message -----
From: Jonathan Borden <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, September 01, 2000 6:49 PM
Subject: Re: XML Schemas/DTD for HealthCare Industry
> Rachel Foerster wrote:
>
>
> >
> > Jonathan,
> >
> > You're right about standard DTD's or Schemas. But you need strong
> datatyping
> > as well for data attributes, allowable codes, etc. To accomplish this
with
> > XML requires mechanisms betyond the DTD, such as namespaces, and then
> > ultimately perhaps links, etc. to where the standard schemas, etc. are
> > avaiable.
>
> I think the XML Schema definition provides for datatyping as well.
> Clearly the reason that HIPAA specified X12 was the immaturity of XML. On
> the other hand XML is quite usable today. I've have implemented strong
> datatyping in projects (for example XMOP:
> http://www.openhealth.org/documents/XMOP.htm )
>
> > All of the robustness currently provided by the X12 standard
> > syntax just is yet there in a full XML architecture. It will get there,
> but
> > not today or tomorrow.
>
> Do you mean literally tomorrow? Because its been a slow week, so
perhaps
> this is true, but once everyone gets back from vacation, I expect that
those
> last few nits in the XML specs and implementations will get solved and
> indeed XML will be *much* more robust than X12 :-)
>
> >
> > Additionally, we don't yet have standard for messaging services XML
> > documents. This is a key component of the ebXML framework currently
being
> > developed by the joint effort between UN/CEFACT and OASIS and on in
which
> > I'm heavily involved.
> >
>
> Correct. ebXML is not yet developed to the extent that would be needed
> for HIPAA but there is much real world work that can be done in XML today.
> As I've mentioned privately in discussing ebXML, the issue about whether
to
> use native XML or MIME multipart/related message wrappers is (IMHO) a
> non-issue because we can still process arbitrary MIME messages using
> SAX/XSLT/DOM via the MIME property set (i.e. XMTP).
>
> I'm a true believer and willing to put my money where my mouth is.
Like
> minded individuals are needed because it is a big project with many
facets.
> The payoff is that we get to work on a Really Good Thing.
>
> Jonathan Borden
> The Open Healthcare Group
> http://www.openhealth.org
>
>
>
>
> ------ XML/edi Group Discussion List ------
> Homepage = http://www.XMLedi-Group.org
>
> Unsubscribe = send email to: [EMAIL PROTECTED]
> Leave the subject and body of the message blank
>
> Questions/requests: [EMAIL PROTECTED]
>
> To receive only one message per day (digest format)
> send the following message to [EMAIL PROTECTED],
> (leave the subject line blank)
>
> digest xmledi-group your-email-address
>
> To join the XML/edi Group complete the form located at:
> http://www.xmledi-group.org/xmledigroup/mail1.htm
>
>
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
