Today a colleague and I went to a potential customer, to discuss our tender. This upcoming project is also going to use HL7 v3.0 schema’s. In the documentation we received I noticed (again) that an organization made their own HL7 v3.0 Xsd implementation. So HL7 v3.0 is described as a standard, but all kinds of dialects arise. That’s a pity. Nothing learned from the past. But that’s my humble opinion.
Tag Archives: BPI
BizTalk User Group Netherlands
the next upcoming BizTalk User Group in the Netherlands is on the 18th of June in Utrecht. Agenda:
* BizTalk Software Factory by Jean Paul Smit and Dick Dijkstra
* BizTalk and SharePoint: 1+1=3 by Gijsbert in ’t Veld and Wesley Bakker (note: same presentation as on Microsoft AP-event in March)
* BizTalk Server 2009 in business by Peter Vervoorn
* and a 4th(unknown yet)
BizTalk Server 2009 released and pricing
This week Microsoft launched BizTalk Server 2009. It is good to see that Microsoft didn’t change the pricing for the several editions (probably because of the crisis). I still think this is very cheap when you compare this to several other ‘middleware’ tools.
BizTalk HotRod, Issue 6, Q2 2009
A new BizTalk HotRod is published. You can find the pdf here.
Again some nice articles, specially about Xslt. When I can’t use the standard functoids, then I also use Validate on the map to get a basic Xslt page. This one I add to the mapper and customize it further.
Pay some extra attention to the Terminator. A nice tool which can be received on request.
And also a great article on FxCop and BizTalkCop!!!
HL7 v3.0 (Dutch version) and BizTalk Server 2009
I added all the HL7 v3.0 schemas to a BizTalk Server project as-is. When I try to build this project, I run into the next problem:
This schema is an invalid XSD Schema and has the following error(s):
1. Type ‘urn:hl7-org:v3:cs’ is not declared, or is not a simple type.
2. Type ‘urn:hl7-org:v3:cs’ is not declared, or is not a simple type.
3. Type ‘urn:hl7-org:v3:cs’ is not declared, or is not a simple type.
4. Type ‘urn:hl7-org:v3:cs’ is not declared, or is not a simple type.
5. Type ‘urn:hl7-org:v3:cs’ is not declared, or is not a simple type.
etc…
With some help from Nictiz it seems that voc.xsd needs a reference to datatypes.xsd.So:
<xs:include schemaLocation="datatypes.xsd"/>
After adding this line, these errors were gone. I ran into some other reference errors. I’ll blog about this in the near future, so stay tuned…
BizTalk Server 2009 installation
I installed BizTalk Server 2009 and all of its features (UDDI, RFID, etc) on my test machine. The setup runs smoothly as expected.
Just one question: where is the final release of the ESB Guidance 2.0?
On a Dutch event (Application Platform in March) Microsoft announced that it would be part of BizTalk Server 2009. I think it will stay a Codeplex product, so Microsoft doesn’t have to give ‘support’ on it. The last months I was playing with the ESB and my experience is that it is still not finished. I had too many problems (see earlier posts). I hope the final ESB Guidance will be released soon, as mentioned on http://www.codeplex.com/esb (coincide with BizTalk 2009 release)
But still: BizTalk Server and the ESB are great and advanced products to work with.
Microsoft BizTalk Server 2009 is available for download
Microsoft BizTalk Server 2009 is available for download on the MSDN Subscribers downloads. The CD/DVD version will probably follow begin may.
ESP.Portal and “A network-related or instance-specific error occurred while establishing a connection to SQL Server”
When I opened the ESB.Portal (BizTalk ESB Guidance 2.0) in Internet Explorer I ran into the next problem:
| Event code: 3005 Event message: An unhandled exception has occurred. Event time: 27-3-2009 20:26:37 Event time (UTC): 27-3-2009 19:26:37 Event ID: f5247af6841e45349be4dbd365417ff9 Event sequence: 99 Event occurrence: 4 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT/ESB.Portal-1-128826538435234595 Trust level: Full Application Virtual Path: /ESB.Portal Application Path: C:\projects\microsoft.practices.esb\Source\Samples\Management Portal\ESB.Portal\ Machine name: myMachine Process information: Process ID: 5752 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: SqlException Exception message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No connection could be made because the target machine actively refused it.) Request information: Request URL: http://localhost/ESB.Portal/Lists/RegistrySummaryContainer.aspx Request path: /ESB.Portal/Lists/RegistrySummaryContainer.aspx User host address: ::1 User: myMachine\user Is authenticated: Trueetc etc |
To fix this you must make sure your SQL connections are configured properly, like:
TCP/IP must be enabled!
HL7 v3.0 in BizTalk Server
The latest HL7 version in BizTalk Server 2009 is 2.5. The newest version is v3.0 and is ‘official’ since 2005. Vendors however are not investing on the new standard, because they invested several years ago in the 2.x standard for their software. So it will take a long time before this new standard is adopted by the market.
The Dutch government implemented HL7 v3.0 standard for the Electronic Health Record (AKA ‘Aorta’). This is a subset from the official ‘standard’ and customized for the Dutch Healthcare (so ‘we’ created our own Xsd’s). Lately I was on the Dutch Health and IT event, and on a seminar there was told that the v3.0 (Xsd’s) is difficult to implement, because it will fail for code generation. Also for BizTalk Server 2009 I had problems with this, so more time has to be spend on this.
I hope to inform you very soon on my progress on this.
===============================
(Dutch version)
De laatste HL7 versie in BizTalk Server 2009 is 2.5. Zo ook in BizTalk Server 2009. De nieuwste versie is v3.0 en is ‘officieel’ sinds 2005. Leveranciers zijn echter niet happig op het investeren in deze nieuwe standaard, omdat ze een aantal jaren terug geïnvesteerd hebben in de 2.x standaard voor hun software. Het zal dus nog een tijdje duren voordat deze nieuwe standaard toegepast zal worden op de markt.
De Nederlandse overheid heeft voor het Electronisch Patiënten Dossier (EPD) HL7 v3.0 geïmplementeerd (ook wel bekend als ‘Aorta’). Dit is een subset van de officiële standaard en aangepast op de Nederlandse zorg (‘we’ hebben dus onze eigen Xsd’s gemaakt). Laatst heb ik de Zorg&ICT beurs bezocht, en daar werd tijdens een mini congres verteld dat v3.0 Xsd’s lastig zijn om te implementeren, omdat code generatie hierop niet zal werken. Ik heb dit zelf ook met BizTalk Server 2009 ondervonden. Daar zal dus meer tijd in gestoken moeten worden.
Ik hoop jullie binnenkort verder te informeren over mijn voortgang.
Delete of ApplicationNode failed: solved
I run into the next problem with BizTalk Server 2009 Beta:
Delete of ApplicationNode failed.
I tried to manual remove the application, but somewhere it’s holding references to non existing resources. This exact message doesn’t give a hit in Google.
UPDATE: Thiago Almeida pointed me on a missing Dll in the GAC. After verifying this, this seems to be the case. After putting all Microsoft.Practices.ESB.Resolver* Dll’s back in the GAC (and a reboot) I was able to remove the application. In the first place I installed the ESB Guidance from the binaries. Later on I uninstalled the ESB, so I could install the ESB and the samples from source code. Probably with the uninstall the application was not removed from BizTalk and still referenced the ‘old’ Dll’s, or the problems occurred because of some manual actions by me after that. Who can tell?
This update is also a nice example what Twitter can mean to you 
Cheers!
