Rachel Foerster wrote:
> There's one other aspect of the HIPAA rules and that relates to data
content
> in addition to format. The transaction set guides also specify the data
> content and the allowable codes as well. Thus, what we will, hopefully,
see
> is a standard format (not your interpretation of the 837 vs mine) as
wellas
> standard data (not your proprietary codes vs mine).
You've said it better than I did. This is the really big win.
>
> Get the standard data into the standard format is a fairly easy task - the
> challenge will be sourcing the standard data first.
>
> Lastly on the issue of using XML -- since XML is extensible that means
that
> the originator of the XML document gets to choose the tag names. Just
> imagine if you would, a situation where each provider generating a health
> care claim chose not only their on tags but data content along with the
data
> attributes. We'd be even worse off then now, with only (!) 450 +/-
> proprietary formats!
Not necessarily. Defining standard XML DTDs and/or Schemata would be to XML
what the HIPAA transaction set guides are to X12. Standard transfer
protocols e.g. HTTP, SMTP, S/MIME are also needed.
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
