Ok - first, I am new to BizTalk...but have been programming about 7+yrs.

I want to feed HL7 message into SQL server - can the HL7 Accelerator and Biz
Talk 2004 be used to process and parse the HL7 messages?

Anyone working in healthcare will know about the HL7 - basically, it is a me
ssage schema.  For ADT messages, some will be for admissions/registrations, 
discharges, updates, transfers, etc...

The real trick I am look for is that BizTalk recognize the message type - an
d then know whether to update a record or to create a new record.  Parsing t
he HL7 message is real pain if handled programatically with sockets and stre
ams...SO...can BizTalk 2004
and the HL7 accelerator do the trick?

[ Post a follow-up to this message ]

This is perfect job for BizTalk!!!

"Kevin Buchanan" <anonymous@discussions.microsoft.com> wrote in message
news:B8FD12BE-7793-43E3-8E1F-95001211F418@microsoft.com...
> Ok - first, I am new to BizTalk...but have been programming about 7+yrs.
>
> I want to feed HL7 message into SQL server - can the HL7 Accelerator and
BizTalk 2004 be used to process and parse the HL7 messages?
>
> Anyone working in healthcare will know about the HL7 - basically, it is a
message schema.  For ADT messages, some will be for
admissions/registrations, discharges, updates, transfers, etc...
>
> The real trick I am look for is that BizTalk recognize the message type -
and then know whether to update a record or to create a new record.  Parsing
the HL7 message is real pain if handled programatically with sockets and
streams...SO...can BizTalk 2004 and the HL7 accelerator do the trick?

[ Post a follow-up to this message ]

>SO...can BizTalk 2004 and the HL7 accelerator do the trick?

Sure. If that's all you want to do with those HL7 messages,
BTS&BTAHL7 might be overkill, though.  BizTalk can do
so much more!

--

[ Post a follow-up to this message ]

Oliver has a point.  If all you want to do is parse HL7, there are some
inexpensive apps that will do this for you, very quickly and efficiently.
On the other hand, if you have more than one place you need to pass the
information to (like billing systems, diagnostic systems, registration
systems, etc) then Biztalk is an excellent choice.  It's not that the tool
is difficult to use (it has a learning curve, but so does anything worth
having)... it's just that Microsoft priced it so high that cost justifying
it is a challenge, especially when using it for simple things like this.

--- Nick
Biztalk Bum

"Kevin Buchanan" <anonymous@discussions.microsoft.com> wrote in message
news:B8FD12BE-7793-43E3-8E1F-95001211F418@microsoft.com...
> Ok - first, I am new to BizTalk...but have been programming about 7+yrs.
>
> I want to feed HL7 message into SQL server - can the HL7 Accelerator and
BizTalk 2004 be used to process and parse the HL7 messages?
>
> Anyone working in healthcare will know about the HL7 - basically, it is a
message schema.  For ADT messages, some will be for
admissions/registrations, discharges, updates, transfers, etc...
>
> The real trick I am look for is that BizTalk recognize the message type -
and then know whether to update a record or to create a new record.  Parsing
the HL7 message is real pain if handled programatically with sockets and
streams...SO...can BizTalk 2004 and the HL7 accelerator do the trick?

[ Post a follow-up to this message ]

Nick:  I agree totally.  We installed the 120 day version yesterday and hope
 to get some communications established today...although I am not exactly 'c
ounting' on it.  The sample version that shipped with the HL7 accelerator di
dn't work.  Maybe we c
an create one (from the "step-by-step" guide) that will work!

I was a little lax with the explanation of what we want it to do...if we can
 get the data into SQL - that is the primary need.  Secondary needs are much
 greater - like physician notification (text paging) for lab results, excess
ing wait times, new arrival
s, etc...(long laundry list here).

-Kevin


----- Nick Malik wrote: -----

Oliver has a point.  If all you want to do is parse HL7, there are some
inexpensive apps that will do this for you, very quickly and efficiently.
On the other hand, if you have more than one place you need to pass the
information to (like billing systems, diagnostic systems, registration
systems, etc) then Biztalk is an excellent choice.  It's not that the tool
is difficult to use (it has a learning curve, but so does anything worth
having)... it's just that Microsoft priced it so high that cost justifying
it is a challenge, especially when using it for simple things like this.

--- Nick
Biztalk Bum

"Kevin Buchanan" <anonymous@discussions.microsoft.com> wrote in message
news:B8FD12BE-7793-43E3-8E1F-95001211F418@microsoft.com...[vbcol=seagreen]
> Ok - first, I am new to BizTalk...but have been programming about 7+yrs. 
BizTalk 2004 be used to process and parse the HL7 messages?[vbcol=seagreen] 
message schema.  For ADT messages, some will be for
admissions/registrations, discharges, updates, transfers, etc...[vbcol=seagreen] 
and then know whether to update a record or to create a new record.  Parsing
the HL7 message is real pain if handled programatically with sockets and
streams...SO...can BizTalk 2004 and the HL7 accelerator do the trick?

[ Post a follow-up to this message ]