No connection could be made because the target machine actively refused it

Event Type: Error
Event Source: BizTalk Accelerator for HL7
Event Category: None
Event ID: 8706
Date: 20/08/2008
Time: 12:55:30
User: N/A
Computer: IN12620
Description:
Unable to log message “An empty batch was received with fr…” to the event log due to exception:
“No connection could be made because the target machine actively refused it 127.0.0.1:4000”.

Username: IN12620\BizTalk
Time: 20/08/2008 12:55:30

The issue, is obvious: The HL7 Logging Service is not running:

ASP.NET MVC Talk in Reading UK July 3rd

I’m in the UK today and tomorrow (on my way back from a trip to India for two days earlier this week), and am giving two tech talks while in town. 

The first is this evening at a London .NET User Group event.  I’ll be presenting Silverlight 3.  Unfortunately the event is already over-registered – so if you haven’t registered yet you’ll need to catch it the next time I’m in town.

The second talk is tomorrow (Friday) from 1-4pm at the Microsoft facility in Reading and is on ASP.NET MVC.  When we first announced it last week it also over-registered quickly.  Thankfully my hosts were able to get a larger room this week, though, so another 120 spots became available. 

You can register to attend the talk for free until 4pm today if you want to attend.  Hurry, though, as there are only 43 seats left (down from 57 seats when I first started writing this blog post).

Hope to see some of you there,

Scott

WCF Exception Shielding Error

While using the WCF Exception Shielding policy in Enterprise Library’s Exception Handler Block to shield exceptions and return Fault Contracts I came across an error. I named the shielding policy “WCF Shielding Policy” and implemented a FaultContract for each type of desired or expected exception.
While testing the policy, we were unable to return a proper […]

HIPAA 4010 to HIPAA 5010 Converter

We have developed a HIPAA 4010 to HIPAA 5010 converter for use in Visual Studio 2008.

After installing the converter, the steps to use the converter are as follows:

  1. Place the appropriate 5010 HIPAA schema in the same project as your current 4010 HIPAA schema
  2. Compile the schema project
  3. Open up map project that references the HIPAA schema project
  4. Right click on the map that needs to be converted
  5. Choose ’Convert to 5010’

It is complete.

Things the converter will do:

  • Create a backup of the current map as {map name}_4010.btm and add it to the project
  • Change the type name of the 4010 map to {type_name}.4010

Here are the screen shots of the tool:

After pressing the Convert to 5010 context menu item the project has the following archived map.

Here is a page from the initial map:

Here is the converted map:

Also for an additional fee, there will be 4010 to 5010 maps and conversely, 5010 to 4010 maps.

Through the contact page, you can pre order this 5010 converter.

I will not be delivering this however, until Microsoft officially releases the HIPAA 5010 schemas.