http://blog.biztalk-info.com - my problems and concurrent resolutions on general BizTalk and other general BizTalk related issues.

http://blog.hl7-info.com - ditto, except for it is just HL7 stuff

See you there…

I downloaded it from here.

It seems pretty easy, actually much easier than the admin tool that I normally have to use to make the entries. Not bad, it is even using the CSS that the site has. I am actually kind of impressed.

The HL7 parser will complain at not finding the ending CR, because it continues to look for it past the EB.

The resolution is simply to leave the CR blank in the adapter configuration and the adapter will work as expected.

Gotta tip your hat to the guys at MS for that bit of functionality!

These are the steps I took to get a custom filename generated from the HIPAA_EDI adapter.

1. Created a property schema with a element defined as a string and have it be a context property
2. Create an schema with the delimiters that will be defined in the HIPAA_EDI send port with an element that repeats 30 times
3. Create both a flat file send pipeline and receive pipeline using the schema defined in step 2
4. Create a single element and associate this element with the element defined in step 1
5. In the orchestration, assign a variable a time
6. From that assigned time do three things in a message assignment
1. Assign the BHT_05 from the variable 
2. Assign a string variable the date as a string in HHMMSSDD format
3. Assign the message with the context property created in the property schema
7. Create a Correllation Type set to the context property
8. Create a Correllation Set defined from Step 7
9. Initialize the Correlation Set in the send shape
10. Have a recieve shape using the message created in step 2 and have a following correlation set
11. Assign the recieved message to a new message and assign the FILE.ReceivedFileName to whatever you want the filename to be
12. Send the newly created message out
13. Deploy
14. Create a temporary folder that you assign the HIPAA_EDI adapter to write to
15. Assign a recieve location to the the folder created in step 14
16. Use the recieve pipeline created in step 3
17. Create a send port using the pipeline created in step 3
18. In the file name use %SourceFileName%
19. Set the directory to the real directory where the HIPAA file is to be placed
20. Bind the logical ports to their respective physical ports

I went to this KB article and configured the SSEE database for remote connections. I was still getting the error on configuration.

What I ended up realizing was that the SSEE database is an orphaned database that should not be installed. I then needed to uninstall the database and re-configure the forms server. Here are the steps to uninstall the Microsoft##SSEE database:

1. In the registry browse to this location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
2. Click on each of the sub folders {GUID} on the left hand column and look at the display name on the right until you see “Microsoft SQL 2005 embedded Edition…”
3. Copy the value that is stored as the UninstallString (for example:  MsiExec.exe /X{0F51A262-1ADF-4914-B448-78AC58C4178A})
4. Open up a command prompt and paste the value and add to the end of the string ” CALLERID=OCSETUP.EXE”
5. Example  c:\Temp\MsiExec.exe /X{0F51A262-1ADF-4914-B448-78AC58C4178A} CALLERID=OCSETUP.EXE

I was continually getting System.OutofMemoryException in the event log.

I read through this article and also this one both sites options did not appeal to me.

Another option is to use custom XSLT instead of the code inside of the map (which seems to stream the entire message into memory).

The solution is actually very easy:

1. Create your map
2. Inside of the mapper, create all of your links, functiods and everything
3. Validate the map
4. Take the XSLT that is generated and add it to your project
5. In the mapper grid, point to the xslt (by following these instructions)
6. Deploy it

It does not process the file very quickly, but it does not error, and I get the output.

This can be done by using the Type Library Importer. An example is here on how to use Tlbimp.exe.

There were great sessions for a whole spectrum of Health Care Professionals, from developers to IT Pros, to management for both the partners and more importantly customers. There were a lot of great things that partners had presented and even more cool things that Microsoft has in store. I did enjoy the other perks that were offered to the attendees, especially the sessionitis I seemed to come down with!

I was very interested in the Connected Health Framework (CHF) and will be blogging about my experiences with my take on best ways to implement the CHF to add additional value to the development life cycle. I don’t think that the CHF is readily available (at least I could not find it), however, as soon as it is published, I will be adding a few entries to my blog.

There are great things going on, and I am glad that I got to be an attendee there. Hopefully I can meet up with you again next time.

The reason for this message is that the orchestration is expecting as the first message part being the MSH segment, whereas it actually finds the BodySegments component. The orchestration then attempts to pick up the message, which is where it errors.

The key to getting this issue resolved is the order that you create the multi-part message.

I know I have made this mistake multiple times, I create the multi-part message type, and renamed the MessagePart_1 to BodySegments, since the IsBodyPart property was already set to true, I then would create the MSHSegment and ZSegments.

This would cause me headaches because the orchestration picking up the message would create the error.

Looking at the code, you have to create the message parts in the correct order. In the Type window, you see the parts in alphabetical order.

However, behind the scenes, it remembers the order that it was created. I have the following excerpt of the odx that shows what is going on behind the scenes: The ADT_A02Type is correct, whereas the ADT_A03Type is incorrect.

So make sure that you create the parts in the correct order and you will not have a problem. If they are created in the wrong order, the only solution I have used is to delete the multi-part message and recreate it again.

By the way, this is only an issue on message that are inbound, outbound messages, the pipeline component is intelligent enought to put things together (even if they are defined in the wrong order), it is the orchestration that consumes the message that is finicky.