Check it out here!

Join us at Booth #13330!

HIMSS Annual Conference & Exhibition
When: February 20 – 24, 2012
Where: Venetian Sands Expo Center, Las Vegas, NV

Click here to learn more!

We are located in Exhibit Hall G at Booth #13330, near the Mobile Health Knowledge Center.

If you would like to RSVP for this event, please email me at angelica.vanderaa@proschconsulting.com by Friday, February 3rd, 2012.

We really hope to see you there!

Please register now to join us for the live Webinar.

Abstract

This 60 minute webinar tells the stories of three unique inpatient/outpatient EMR integration projects:
• IDN continuity of care between specialists and hospitals
• Hospital to physician’s group billing integration
• Regional hospital outreach to community physicians

We will talk through the drivers behind each project, their technology, struggles, and in hind sight, what could have gone better.

If you are looking for answers to any of the following questions, you are in the right place:
• What makes sharing information between hospital and ambulatory EMRs such a pain?
• When does discreet data matter?
• What role can a regional HIE play in enterprise integration?
• With so many stakeholders, points of view, unknowns, and competing projects, how do we ensure we get the outcome we need without adding a hundred more meetings?

We will do a quick introduction to HIE technologies including CCD, XDS.b, PIX, and HL7.

Presenters

Lee Prosch – Managing Partner, Prosch Consulting
Tony Nuzzo – Vice President, Prosch Consulting

Reach out to me at 630-701-9036 or angelica.vanderaa@proschconsulting.com if you have any questions. We hope you can join us!

Angelica Vander Aa
Sales & Marketing Coordinator, Prosch Consulting

Please register now to join us at 10:30 Central time.

I have been using ILSpy for the past couple of weeks. It doesn’t have the same plugin system and some of the reflected code looks still has a lot of IL looking code in it (goto statements, etc.), but for such a new tool, it works tremendously.

So, if you are looking for an alternative to .Net Reflector, I would recommend ILSpy.

Download: http://wiki.sharpdevelop.net/ilspy.ashx

This tool can be pretty helpful when trying to cleanup CRUFT. In addition, there are also a handful of helpful performance tuning scripts and general management scripts. This is a must use for BizTalk administrators.

Here are updated instructions for configuring this setting on BizTalk 2009 and 2010 installations.

1. Open RegEdit
2. Navigate to the following path:
   • BizTalk 2009 (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Accelerator for HL7\Version 2009
   • BizTalk 2009 (64-bit): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Accelerator for HL7\Version 2009
   • BizTalk 2010 (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Accelerator for HL7\Version 2010
   • BizTalk 2010 (64-bit): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Accelerator for HL7\Version 2010
3. Add a new DWord Value
   • MLLPSendFlushTimeout
   • For the value, select Decimal and then provide a value between 500-1,000
4. Restart all host instances that use the MLLP adapter for the updated configuration to take place

I wrote up a quick sample application that converts .Net objects into XDocuments using XmlSerializer. This code is not perfect and I can imagine that objects that contain circular references will blow up. DataContractSerialization may be a better option for that. More information on de/serialization at Microsoft.

For converting XmlDocument to XDocument, I used some of the suggestions from Marcelo Lopez Ruiz’s blog post Fast way to convert XmlDocument into XDocument.

C# – Object to XDocument

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Xml.Linq;
using System.IO;
using System.Xml.Serialization;
using System.Xml;

namespace Utilities
{
    public static class Serialization
    {

        public static T Deserialize<T>(StringReader dataIn)
        {
            return (T)(new XmlSerializer(typeof(T), String.Empty)).Deserialize(dataIn);
        }

        public static XDocument Serialize(object obj)
        {
            // Serialise to the XML document
            var objectDocument = new XmlDocument();

            using (XmlWriter writer = (objectDocument.CreateNavigator()).AppendChild())
            {
                (new XmlSerializer(obj.GetType())).Serialize(writer, obj);
                writer.Close();
            }

            return XDocument.Load(new XmlNodeReader(objectDocument));
        }

        public static T Open<T>(string fileName)
        {
            if (String.IsNullOrEmpty(fileName))
                throw new ArgumentNullException("fileName");

            if (!File.Exists(fileName))
                throw new FileNotFoundException("The provided file does not exist.", fileName);

            return (Serialization.Deserialize<T>(new StringReader(fileName)));
        }

        public static void Save(object obj, string fileName)
        {
            if (String.IsNullOrEmpty(fileName))
                throw new ArgumentNullException("fileName");

            if (!File.Exists(fileName) && !Directory.Exists(Path.GetFullPath(fileName)) && !(Directory.CreateDirectory(fileName)).Exists)
                throw new DirectoryNotFoundException(String.Format("The provided Directory does not exist or cannot be created."));

            (Serialization.Serialize(obj)).Save(fileName);
        }
    }
}

VB.Net – Object to XDocument

(Note: This code was generated from a converter and has not been tested.)

Imports System.Collections.Generic
Imports System.Linq
Imports System.Text
Imports System.Xml.Linq
Imports System.IO
Imports System.Xml.Serialization
Imports System.Xml

Namespace Utilities
	Public NotInheritable Class Serialization
		Private Sub New()
		End Sub

		Public Shared Function Deserialize(Of T)(dataIn As StringReader) As T
			Return DirectCast((New XmlSerializer(GetType(T), [String].Empty)).Deserialize(dataIn), T)
		End Function

		Public Shared Function Serialize(obj As Object) As XDocument
			' Serialise to the XML document
			Dim objectDocument = New XmlDocument()

			Using writer As XmlWriter = (objectDocument.CreateNavigator()).AppendChild()
				(New XmlSerializer(obj.[GetType]())).Serialize(writer, obj)
				writer.Close()
			End Using

			Return XDocument.Load(New XmlNodeReader(objectDocument))
		End Function

		Public Shared Function Open(Of T)(fileName As String) As T
			If [String].IsNullOrEmpty(fileName) Then
				Throw New ArgumentNullException("fileName")
			End If

			If Not File.Exists(fileName) Then
				Throw New FileNotFoundException("The provided file does not exist.", fileName)
			End If

			Return (Serialization.Deserialize(Of T)(New StringReader(fileName)))
		End Function

		Public Shared Sub Save(obj As Object, fileName As String)
			If [String].IsNullOrEmpty(fileName) Then
				Throw New ArgumentNullException("fileName")
			End If

			If Not File.Exists(fileName) AndAlso Not Directory.Exists(Path.GetFullPath(fileName)) AndAlso Not (Directory.CreateDirectory(fileName)).Exists Then
				Throw New DirectoryNotFoundException([String].Format("The provided Directory does not exist or cannot be created."))
			End If

			(Serialization.Serialize(obj)).Save(fileName)
		End Sub
	End Class
End Namespace

I received a request to help reconfigure a BizTalk server and point it to a new BizTalk group and reconfigure the BizTalk HL7 Accelerator to use the new SQL Server as well. Reconfiguring the Primary BizTalk server went as smooth as to be expected, but when we went to reconfigure the BizTalk server, we ran into a strange issue regarding the database server. Everything was going fine, until we came to configuring the Auditing and Logging Database. The database name will still set to the old server (in our case it ended with 0144).

I checked the file system and couldn’t find any reference to the old server. I, also, did a quick scan of the Registry for the old server name, but came up with nothing. I decided to open up the installation MSI with ORCA and I found a registry setting that looked promising.

I checked the registry again, but I couldn’t find the registry setting. This is installed on a 64-bit Windows Server 2008 R2 server, so 32-bit components are stored separately in the registry (more information at Microsoft). Looking in the Wow6432Node, I finally found the registry setting that was causing the issue.

Windows Server 2008 64-bit Registry Path / Key Name:

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Accelerator for HL7
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Accelerator for HL7\Version 2009\Setup

Windows Server 2008 32-bit Registry Path / Key Name:

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Accelerator for HL7
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Accelerator for HL7\Version 2009\Setup

After making the changes to the DbConnStr and DatabaseServer registry entries, I was able to re-run the installer and this time the configuration came up with the correct database server.

I am not sure how often this situation comes up, but it has come up at least twice for me. Let me know if you have any questions.