|
Home > Archive > BizTalk Server Applications Integration > May 2004 > HIPAA Integration to SQL Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
HIPAA Integration to SQL Server
|
|
| Dean Shoultz 2004-05-11, 8:21 pm |
| Thank in Advance for the help...
I have a rather mature SQL Server database that adjudicates claims for a PPO. I need to be able to take the claim information and put it into an 837 format that can be transmitted to a payor. My SQL DB contains a header/detail relationship for the claim.
The detail table contains one or more procedure codes.
I only need to produce the most basic form of this, and any help or guidance would be appreciated. I am willing to compensate anyone who is willing to help me.
Thanks,
Dean
| |
| larry franks 2004-05-11, 8:21 pm |
| Hi Dean, have you looked at that BizTalk adapter for SQL? With this you
can pull records from a SQL database into an XML schema. You should be
able to use this against a stored proceedure to pull back the data you
need, then map this over to the outbound HIPAA document.
Larry Franks
This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| Thread-Topic: HIPAA Integration to SQL Server
| thread-index: AcQ0Qrop4bu9KeoHQI21WjEkpwDHkA==
| X-WN-Post: microsoft.public.biztalk.appintegration
| From: =?Utf-8?B?RGVhbiBTaG91bHR6?= <dshoultz@advancedsoftware.com>
| Subject: HIPAA Integration to SQL Server
| Date: Fri, 7 May 2004 07:51:06 -0700
| Lines: 7
| Message-ID: <A6929D12-A741-45AC-9B9C-D07DBE12689E@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.biztalk.appintegration
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.appintegration:6648
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.biztalk.appintegration
|
| Thank in Advance for the help...
I have a rather mature SQL Server database that adjudicates claims for a
PPO. I need to be able to take the claim information and put it into an 837
format that can be transmitted to a payor. My SQL DB contains a
header/detail relationship for the claim. The detail table contains one or
more procedure codes.
I only need to produce the most basic form of this, and any help or
guidance would be appreciated. I am willing to compensate anyone who is
willing to help me.
Thanks,
Dean
|
| |
|
| Hi Dean,
We are in similar boats. What I would suggest is:
1. Depending on the complexity of your database architecture, create a FOR XML AUTO or FOR XML EXPLICIT sproc to put out the xml for mapping to an 837.
2. If you are able to shape your data the way you would like with the AUTO option (I could not - had to use EXPLICIT), you can have the luxury of using the 2004 SQL Adapter generate a schema for you. If you have to use EXPLICIT, you could still start wi
th an autogenerated xsd, and modify it.
3. Map from your xsd to 837 spec. While this mapping can be done in 2004, an 837 will not validate as X12 v4010A1, and 837's in general, are not yet supported in BTS 2004.
4. To get your data out of the database, you can either use the SQL adapter to pull it out (although I am not sure this is possible if using XML EXPLICIT), or you can set up a Windows Task Manager job to execute a C# or VB project that uses an XMLText re
ader to run your sproc (use .ExecuteXMLReader()) and load up and save an XML document to a file location.
You could then use a file adapter to pull your xml doc into the orchestration to be transformed.
JT
|
|
|
|
|