BizTalk Server General - Creating an HL7 MSHSegment

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server General > March 2005 > Creating an HL7 MSHSegment





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 Creating an HL7 MSHSegment
Matt Cable

2005-01-13, 2:50 am

Is it possible to create a MSH Segment in the HL7 Accelerator without
building it in an Orchestration (like shown in the Message Enrichment
tutorial)?

My goal is to transform a flat file into a DFT completely in BizTalk
Messaging. Currently, I am getting the error - "Reason: Message does not
contain a part with name MSHSegment". Which is understable because it
doesn't exist anywhere yet. But is there any other functionality
(especially non-orchestration, possibly in the BTAHL7 Config Explorer?) that
I am missing that could build it? Possibly based upon the "MSH Map" tab in
that Explorer.

Thanks,
Matt



Suren

2005-01-26, 5:54 pm

The only other location i can think of appening a MSH segment in messaging is
using a custom pipeline component to append a hard coded MSH string to the
data DFT data segements.

If this is a flat file you could try this out in the HL7 Recv Pipeline prior
to the HL7 DASM component

"Matt Cable" wrote:

> Is it possible to create a MSH Segment in the HL7 Accelerator without
> building it in an Orchestration (like shown in the Message Enrichment
> tutorial)?
>
> My goal is to transform a flat file into a DFT completely in BizTalk
> Messaging. Currently, I am getting the error - "Reason: Message does not
> contain a part with name MSHSegment". Which is understable because it
> doesn't exist anywhere yet. But is there any other functionality
> (especially non-orchestration, possibly in the BTAHL7 Config Explorer?) that
> I am missing that could build it? Possibly based upon the "MSH Map" tab in
> that Explorer.
>
> Thanks,
> Matt
>
>
>
>

Matt Cable

2005-03-02, 8:47 pm

Can I request some sort of MSH generation in a future version. Otherwise it
looks like everyone is going to have to roll their own code to create unique
identifiers in this segment. I've got a little kick back from it already.

Thanks,
Matt

"Suren" <Suren@discussions.microsoft.com> wrote in message
news:B85E7950-84B4-4168-A1B1-462E82735110@microsoft.com...[vbcol=seagreen]
> The only other location i can think of appening a MSH segment in messaging
> is
> using a custom pipeline component to append a hard coded MSH string to the
> data DFT data segements.
>
> If this is a flat file you could try this out in the HL7 Recv Pipeline
> prior
> to the HL7 DASM component
>
> "Matt Cable" wrote:
>


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com