Upgrade to .NET Standard and Version Scheme Changes

It has been a while since I've posted a new topic on the blog, and given that there is a major announcement of SanteDB I figured this would be a perfect opportunity.

As you may (or may not) be aware, SanteDB is based on the OpenIZ CDR codebase. OpenIZ started way back in 2015 on .NET Framework 4.5, and a commercial version of Xamarin (remember when that was a thing?). Unfortunately, to realize the goal of reusable platform components, this meant that OpenIZ needed to be written in Portable Class Library (PCL) technology.

Well, Microsoft has deprecated PCL for quite some time now, and finally have removed the template types from Visual Studio 2019. This necessitated the upgrade of SanteDB from PCL to .NET Standard 2.0 (which also required an update to the server to .NET Framework 4.7).

These new, refactored SanteDB packages are marked as 2.0. These package versions (currently 2.0.6) are for the Jasper packaging / major version of SanteDB. You should be able to upgrade your references to these new packages as none of namespaces have changed and it largely remains compatible with 1.1xx code.

You will, however, need to update your configuration files, these include:

• The core server configuration file santedb.config.xml
• Any dCDR configuration files (usually in %appdata%\SanteDB)

The changes required involve updating the version string, for example, where you once had:

<services>
     <add type="SanteDB.Core.Serivces.Impl.XXXXX, SanteDB.Core, Version=1.129.0.0"

You should replace the reference to 2.x

<services>
    <add type="SanteDB.Core.Serivces.Impl.XXXXX, SanteDB.Core, Version=2.0.0.0"

We will be packaging a new series of installers for 2.x branch (SDK, Server, DCG, etc.) in the coming week

MEDIC CR / SanteMPI 1.4 Released

Today, the SanteSuite community released version 1.4.0 of MEDIC CR (SanteMPI 1.x). This release includes several features related to operationalizing the MPI/CR software using authentication mechanisms other than two-way TLS and X509 certificates. With this release it is possible to authenticate clients on HL7v2 and HL7 FHIR streams using an OAUTH2 bearer token.

For HL7 FHIR, any valid BEARER token should be used in JWT format.

For v2 messages, authentication occurs against a compatible OAUTH2 service. Compatible OAUTH2 services should support the X-Device-Authorization header. The device credentials are a  combination of MSH-3|MSH-4 and MSH-8.

The 1.4.1 update will also introduce the ability to use standard username/password grants.

Check out the release on GitHub: https://github.com/santedb/client-registry/releases/tag/v1.4.0