Release notes

Important

The release notes are moved to firely-net-sdk/releases.

The 2.0 transition docs can be found here.

1.3.0 (STU3, R4) (released 20190710)

Bugfixes

447/791 Disabled incorrect invariant rng-2 on Range datatype.
594 Suppressed useless information and warnings about non matching slices when slicing succeeds.
659 WebRequest task stays alive and holds connection after TimeoutException is thrown.
865 Validator accepted instant types without timezone
880 DirectorySource should not only detect but also report duplicate file names.
883 ZipSource is not handling files in subdirectories.
889 Annotated Additional Validation Rules would get confused by hybrid typed/untyped ITypedElement trees
895 DirectorySource should internally expand specified content directory to a full path to make matching reliable.
913 NavigatorStreamFactory (and thus DirectorySource) threw lots of caught exceptions, causing slow-down of directory scanning.
930 Summary and _elements now include non-mandatory children of mandatory top-level elements
933 Binding validation now returns success when validating a an non-bindeable instance
936 Internal ITypedElement implementation of Location property differed from the one in ElementNode.
941 The settings parameter was ignored for the xml and json serializer
965 Snapshotgenerator for R4 will now make typeref.(target)Profile replace base, not merge.
1002 Validation still enforced that contained resources cannot have text in R4.
1003 _sort did not allow the use of underscore search parameters.
1013 FhirClient threw incorrect kind of Exception when reading a non-FHIR body.

New Functionality

293 There is now a setting to ensure serialized files always end with newline
631 FhirClient gives a more informative error message when encountering an unparseable LastModified header
632 Improve validation of coded elements with null flavours
748/749 Expose ParserSettings and ExceptionNotificationHandler from Resource resolvers
750 Add ParserSettings to WebResolver
790/1016 ElementNode will now let you insert and delete nodes
890 NavigatorStream can now also return resources without an Id
892 ArtifactSummaryGenerator will now return error summaries together with file information
904 ArtifactSummary should indicate which entries are Bundles.
917 Validator now accepts custom resources
929 FhirClient now has support for “async” operations needed for bulk data.
938 Added factory methods on ElementNode to create primitive nodes implementing ITypedElement.
944 FhirUrl now implements IStringValue.
958 Allow Issue properties to be modified
959 FunctionCallExpression nodes can now be used without a Focus expression
992 Errors on FhirPath invariants now display structure definition and key for debugging purposes.
995 Re-enabled support for slicing by “pattern”.

Note: Active development of DSTU2 has stopped, the included DSTU2 1.3 update is there to retain binary compatibility with the newer shared assemblies but has none of the new features.

1.2.1 (STU3, R4) (released 20190416)

The fix for issue #889 should have been in version 1.2.0, but it was not because of a merge error. In this hotfix (1.2.1) we corrected this mistake and added the fix for issue #889.

Bugfixes

#889 Additional rules will get confused by hybrid typed trees

1.2.0 (DSTU2, STU3, R4) (released 20190329)

New Functionality

Support for R4 final (4.0.0)
#748 You can now set the ParserSettings used by the DirectorySource
#756 Type-aware validations can now also be run by the POCO parser
#924 Performance improvements

Bugfixes

#907 Transaction code documentation was wrong
#833 FhirClient.Read would return null when server not responding
#896 StructureDefinitionElementDefinitionSummaryGenerator would not always derive IsRequired correctly
#889 Additional rules will get confused by hybrid typed trees
#888 TypedElementToSourceNodeAdapter should return ISourceNode annotation
#872 Quantity now binds to <code>, not <unit>

Note: The parsing subsystem now catches way more error in the FHIR xml/json syntax. Since this would raise errors in instances that previously parsed without problems, this feature is turned off by default. Turn it on by setting ParserSettings.PermissiveParsing to “false”.

1.2.0-beta2 (DSTU2, STU3, R4) (released 20190228)

Because of a mistake in creating the release of 1.2.0-beta1 for STU3, this beta1 release was not correct. The other 1.2.0-beta1 releases (DSTU2 and R4) were properly released. In STU3 you got a System.MissingFieldException during parsing a resource from xml to poco. This has been fixed now.

Fix: Parsing of the primitive type decimal is done better now.

1.2.0-beta1 (DSTU2, STU3, R4) (released 20190220)

This first beta of 1.2 includes support for FHIR version R4! In the coming period we will investigate the performance of this release and take the last bugs out (if there are any :) ). We will probably release a second beta, or if we are real confident about this beta1, we will create a final release 1.2.0.

Fix: #750 The WebResolver should allow clients to configure custom ParserSettings for de-serialization
Fix: #748 The DirectorySource should allow clients to configure ParserSettings for de-serialization
Fix: #863 ParserSettings.Clone() does not copy PermissiveParsing
#846 Enable cross-platform development
Fix: #814 Empty contained block leads to NullReferenceException
Fix: #824 Type-slice shortcut for choices in R4 does not yet work
Added: #853 R4 Snapshot Generator
Fix: #854 ElementDefinition.Base component #854
Fix: #864 Validation of References to contained resources where there are multiple potential types, and the contained resource is not the first one targeted.
Fix: #827 [Snapshot Generator] Child constraints are not included in snapshot when constraining a .value element
Fix: #820 Fixed IgnoreUnknownElements naming inconsistency
Improvement: #821 Better error reporting by always mentioning the context of the error
Fix: #725 Debugger display doesn’t work as the property has been renamed
Fix: #817 Setting an empty Meta object breaks Json Serialization
Fix: #756 Validation issue with text.div
Fix: #807 FhirPath indexOf returns -1 instead of empty.

1.1.3 (DSTU2, STU3) (released 20190213)

Hotfix release

Fix: ParserSettings.PermissiveParsing was not copied in Clone() and constructor

1.1.2 (DSTU2, STU3) (released 20190131)

Hotfix release

Fix: v2-tables.xml of specification.zip contained an invalid codesystem (id =v2-0550)

1.1.1 (DSTU2, STU3) (released 20190130)

Hotfix release

#817 Setting an empty Meta object breaks Json Serialization
Fix: Added PermissiveParsing setting to ParserSettings
Fix: Setting primitives to null AND using extensions would crash ITypedElement.Value

Note: Since 1.0, the parsers are more strict than before in what they accept as input. To disable this behaviour, set PermissiveParsing to ‘true’ in the ParserSettings which can be passed to the Json/Xml POCO parsers.

1.1.0 (DSTU2, STU3) (beta - final version to be released 20190128)

This is a minor release.

### New functionality

#180 We added a method to rerieve a contained resource on the parent resource by url.
#460 Add support for _elements on the POCO serializer
#731 FhirDateTime.ToDateTimeOffset() now asks you to pass in a TimeSpan - previously UTC was assumed.
#578 DirectorySource will now resolve a specific version of a conformance resource if the canonical is versioned.
#726 Add type-less overload for the POCO Parse() methods to mean “expect any resource type”.
#773 Added new FhirPath functions to support new invariants in R4.

### Bugfixes

#339 The Patient search parameter for some resources had an incorrect target list in ModelInfo
#553 The namespace of the internal Sprache parser in the FhirPath assembly has been moved to a new namespace to avoid conflicts when also using the external assembly.
#559 The LocalTerminologyService no longer throws an exception when there is no code at all passed to it.
#561 The FhirPath compiler keeps a cache of recently encountered expressions. Multi-threaded access to it has been sped up.
#624 Validator will now give a warning instead of an error if the display in a code is different from the one in the codesystem.
#718 Corrected ‘|’ or “or” in invariants in DSTU2/STU3.
#732 Json serialization no preserves significant digits.
#746 ModelInfo.IsCoreModelTypeUri did not handle relative urls well.
#754 Roundtripping patient.ToTypedElement().ToPoco<Patient>() failed.
#755 Arguments to FhirClient.Search() with a key/value pair without value would throw an exception.
#793 Element and Backbone element were handled differently in the ClassMappings that feed the parsers.
#794 GetResourceFormatFromContentType would throw a null reference exception when the content-type had non-alphanumeric characters.

1.0.0 (DSTU2, STU3) (20181217)

This large release fixes about 80 issues - but more importantely introduces a completely new parsing/serialization subsystem that allows you to work without POCOs and also is more strictly following the serialization rules for XML and Json. This means you will get parse errors on instances that where (incorrectly) accepted as correct by the older versions of the API. More information on the new parsing subsystem can be found in the documentation. Please note that we have strived to keep the exsiting top-level POCO-parsing API intact - your projects should still compile without problems.

#248 Json output can now be formatted
#356 Parsing/serialization subsystem replaced to support working without using the generated POCO classes.
#400 TransactionBuiler.Delete would cause “Invalid resource URL” in some circumstances.
#433 Made the interface of all settings-related classes consistent across the whole API surface.
#483 Introduction of IErrorSource to facilitate forwarding of errors and warnings between components of the API.
#538 Summary=true still let some non-issummary fields through
#569 Prefer header was not set on PUT
#593 Fix .ttinclude file to prevent generating errors in some build environments.
#619 Snapshot Generator ignores multiple codings with only display value
#627 ToFhirDateTime() produced dateTimes without timezones when input DateTime.Kind was Unspecified
#639 Target platforms are now 4.5, Netstandard 1.1, Netstandard 2.0
#642 SnapshotGenerator does not expand custom element profile on Reference
#657 Json Serializer was losing accuracy on serializing DatetimeOffset (last 4 digits in ticks)
#663 Faster generation of property getters/setters with reflection emit
#670 DifferentialTreeConstructor can now be used publicly to turn sparse differentials into full trees
#676 Speed-up of serializers when running in Debug mode
#684 DirectorySource can now retrieve summary data given a specific filename
#696 SummaryGenerator now also extracts the extension context
#704 Replaced uses of .NET DateTime with DateTimeOffset everywhere in the public API surface.
Build scripts changed because of migration to Azure DevOps from AppVeyor

0.96.1 (Just R4) (released 20180925)

R4-only release with all changes to the spec included upto the September ballot release.

Note: There are no new packages for other versions, since we did not add any new functionality.

0.96.0 (DSTU2, STU3 and R4) (released 20180606)

#595 Added capability to harvest metadata directly from a stream
#524 Search paths no longer use [x] suffix in DSTU2
#556 Fixed threading issues in valueset expansion and snapshot generation when using the CachedResolver
#577 FhirBoolean.value no longer has incorrect [BooleanPattern] in R4
#591 Added ignoreCase option for parsing to enums
#599 Fixed threading issue in FhirPath engine
#601 Made the DifferentialTreeConstructor class public
#606 FhirPath evaluator now support Resource and DomainResource as path roots
#612 Bugfix for snapshot generator
#614 Improved encoding for search parameters when doing POST-based search

0.95.0 (DSTU2, STU3 and R4) (released 20180412)

Added support for R4 (warning: early alpha - client connectivity and parsing/serialization only)
Added a SnapshotSource resource resolver that creates snapshots on the fly
Added functionality to quickly harvest metadata from conformance resouces on a file system
#423 Internal references within contained resources are not validated properly
#474 Validation fails when start date is 0001-01-01
#477 ZipSource is extracting the content in a temp directory without a discriminator for the spec version
#479 Use search using POST
#454 Invoking an operation using GET (i.e. $everything) does not work with primitive type as parameters.
#494 Directory Source - single threaded by default
#461 Check support for both types of extensions for regexes on primitive values (tracker GF#12665)
#510 Missing diff annotation on ElementDefinition.TypeRefComponent
#536 FhirClient.Transaction() method incorrectly POSTs to FHIR Base URl with trailing slash
#544 Date.ToDateTime failed to convert “1976-12-12”
#557 workaround for slice validation when discriminator is missing in slice
#571 Serialize to XDocument and JObject directly

0.94.0 (DSTU2 and STU3) (released 20171207)

#448, the FhirXmlSerializer/FhirJsonSerializer should now be instantiated, use of the static FhirSerializer class is obsoleted
#434, the API is no longer creating empty <meta> tags in the serialization
#420, the json parser no longer returns -1,-1 for positions on errors
#412, added support for read-through and cache invalidation to CachedArtifactSource
#355, the POCO parser is now using IElementNavigator as a source
#474, fixed a bug where the parser would not accept ‘01-01-01’ as a date
#371, the validator will now complain when it encounters unsupported discriminator types
#426, when you tell the validator to not follow external references, it will no longer produce warnings that it cannot locate the external references.
#489, the validator would sometimes report incorrect indices in paths with repreating elements
#477, the location where the specification.zip is unpacked now includes the version in the name, thus avoiding conflicts when switchin branches between dstu2/stu3 at development time
#419, calling $everything with no parameters will no longer result in an incorrect http request.

0.92.5 (DSTU2) / 0.93.5 (STU3) (released 20171017)

Changes to both versions:

Changed the IElementNavigator interface to enable skipping directly to a child with a given name, thus increasing navigation performance
Improved performance of validation and fhirpath for POCOs
Split off IFhirClient interface from the FhirClient implementation (primarily for testing/mocking)
Many smaller bugfixes
Improved error messages produced by the validator based on input from the NHS UK
The validator will now let you put a constraint on children of Resource.contained, Bundle.entry.resource and similar nested resources.
SerializationUtil.XmlReaderFromString() will no longer try to seek the stream passed in and rewind it.
TransactionBuilder now has a (default) argument to specify the type of Bundle to build. Thanks mbaltus!
DirectorySource now has Include/Exclude patterns (with globs) to have more control over directory scans for resource files.
DirectorySource now supports processing conformance resources in json
FhirClient now has async support
You can now have List<> properties (like Extensions and other repeating elements) with null elements - these will simply be ignored and not serialized. Thanks wdebeau1!
Made date to string and string to date conversion more consistent, fixing problems with locales using something else than ‘:’ for time separators.
Fixed an error where the If-None-Exists header included the base url of the server. Thanks angusmiller+tstolker!
All Search() overloads on FhirClient now also have a reverseInclude parameter
Update with a conditional would not set the If-Match header when doing a version-aware update. Thanks tstolker!
DeepCopy() did not actually deep-copy collections - if you changed the original collection before you iterated over the clone, you would see the changes. This has been fixed. Thanks mattiasflodin!
Client would not pass on 1xx and 3xx errors to client, instead throwing a generic NotSupported exception, making it harder to handle these errors by the client. Thanks tstolker!
Added a fall-back terminology service so the validator can now invoke an external terminology service if the local in-memory service (provided with the API) fails.
You can now specify a binding on an Extension, which translates to a binding on Extension.value[x]
Fixed a bug where -if the definition of element[x] had a binding and a choice of bindeable and non-bindeable types- the validator would complain if the instance was actually a non-bindeable type.
BREAKING: FhirClientOperation.Operation has been renamed to RestOperation
BREAKING: Revision of calls to terminology services to support all parameters and overloads
Validation across references will now include the path of the referring resource in errors about the referred resource to make interpretation of the outcomes easier.
FhirPath’s resolve() now actually works, and will resolve contained/bundled resources in the instance under evaluation. This also means the FhirPath evaluator will now take an EvaluationContext in which you can pass your resolver over to the evaluator.
The enums in the generated code now also have an attribute on them with information about the codesystem, which can be retrieved using GetSystem() on any enum. Thanks brianpos!
Added a few specific [Serializable] attributes to make the POCOs serializable with the Microsoft Orleans serializer. Thanks alexmarchis!
Several improvements & bug fixes on the SnapshotGenerator
Fixed handling of non-fhir json files in the conformance directory.
Fixed eld-16 constraint, which used an invalid regex escape (\_)
Now using the new NuGet 3.3 <contentFiles> tag to replace the (failing) install.ps1, so a) you’ll get the new specification.zip transitively in dependent projects and b) the build action will be correctly set.

DSTU2:

Fixed small errors in the generated ConstraintComponent properties, giving more correct validation results

DSTU3:

Fixes to the snapshot generator to create better ElementDefinition ids
_sort parameter now uses STU3 format (_sort=a,-b,c) instead of modifier
You can now set the preferred return to OperationOutcome. Thanks cknaap!
You can now request the server to notify the client about unsupported search parameters. Thanks tstolker!

Changes to the DSTU2 version:

Fixed small errors in the generated ConstraintComponent properties, giving more correct validation results

Changes to the STU3 version:

Fixes to the snapshot generator to create better ElementDefinition ids
_sort parameter now uses STU3 format (_sort=a,-b,c) instead of modifier
You can now set the preferred return to OperationOutcome. Thanks cknaap!
You can now request the server to notify the client about unsupported search parameters. Thanks tstolker!

0.90.6 (released 20160915)

Fix: FhirClient will no longer always add _summary=false to search queries
Fix: FhirClient will not throw parse errors anymore if the server indicated a non-success status (i.e. a 406)

0.90.5 (released 20160804)

Enhancement: Portable45 target includes support for validation, and no longer depends on Silverlight 5 SDK. Thanks Tilo!
Enhancement: Support for serialization where _summary=data (and automatically adds the Subsetted flag - temporarily adds the Tag then removes after serialization, if it wasn’t there already)
Enhancement: Added Debugger Displays for commonly used types
Enhancement: Debugger Display for BundleEntries to show the HttpMethod and FullURL
Enhancement: Additional method public static bool IsKnownResource(FhirDefinedType type) in ModelInfo (Thanks Marten)
Enhancement: You can (and should) now create an instance of a FhirXmlParser or FhirJsonParser instead of using the static methods on FhirParser, so you can set error policies per instance.
Enhancement: Introduced ParserSettings to configure parser on a per-instance basis:

FhirXmlParser parser = new FhirXmlParser(new ParserSettings { AcceptUnknownMembers = true });
var patient = parser.Parse<Patient>(xmlWithPatientData);

Enhancement: Introduced a setting to allow parser to parse (and serialize) unrecognized enumeration values. Use Code<T>.ObjectValue to get to get/set the string as it was encountered in the stream. The FhirClient now has a ParserSettings property to manage the parser used by the FhirClient.
Enhancement: By popular demand: re-introduced FhirClient.Refresh()
Enhancement: Snapshot generator now supports all DSTU2 features (re-slicing limited to extensions)

ArtifactResolver source = ArtifactResolver.CreateCachedDefault();
var settings = new SnapshotGeneratorSettings { IgnoreMissingTypeProfiles = true };
StructureDefinition profile;

var generator = new SnapshotGenerator(source, _settings);
generator.Generate(profile);

Fix: Status 500 from a FHIR server with an HTML error message results in a FhirOperationException, not a FormatException. Thanks Tilo!
Fix: Code<T> did not correctly implement IsExactly() and Matches()
Fix: Now parses enumeration values with a member called “Equals” correctly.
Fix: Base.TypeName would return incorrect name “Element” for Primitives and Code<T> (codes with enumerated values)
And of course numerous bugfixes and code cleanups.

0.90.4 (released 20160105)

Enhancement: Additional Extension methods for converting native types to/from FHIR types

public static DateTime? ToDateTime(this Model.FhirDateTime me)
public static DateTime? ToDateTime(this Model.Date me)
public static string ToFhirDate(this System.DateTime me)
public static string ToFhirDateTime(this System.DateTime me)
public static string ToFhirId(this System.Guid me)

Enhancement: Added the SnapshotGenerator class to turn differential representations of a StructureDefinition into a snapshot. Note: we’re still working with the Java and HAPI people to get the snapshots 100% compatible.
Breaking change: All BackboneElement derived classes are now named as found on BackboneElement page in the specification, under the specializations heading. Usual fix for this will be removing the resource typename prefix from the classname, e.g. Bundle.BundleEntryComponent -> Bundle.EntryComponent
Fix: Elements are not serialized correctly in summary mode
Fix: Validate Operation does not work
Fix: DeepCopy does not work on Careplan f201
Fix: SearchParameters in ModelInfo are missing/have invalid Target values

From this version on, the model is now code generated using T4 templates within the build from the specification profile files (profiles-resources.xml, profiles-types.xml, search-parameters.xml and expansions.xml)

0.90.3 (released 20151201)

Enhancement: IConformanceResource now also exposes the xxxElement members. Thanks, wmrutten!
Enhancement: Parameters.GetSingleValue<> now accepts non-primtives as generic param. Thanks, yunwang!
Enhancement: ContentType.GetResourceFormatFromContentType now supports charset information. Thanks, CorinaCiocanea!
Enhancement: Operations can now be invoked using GET
Fix: Small code analysis fixes. Thanks, bnantz!
Fix: SearchParams now supports _sort without modifiers. Thanks, sunvenu!
Fix: FhirClient: The “Prefer” header was never set. Thanks, CorinaCiocanea!
Fix: FhirClient could not handle spurious OperationOutcome results on successful POST/PUT when Prefer=minimal. Thanks, CorinaCiocanea!
Fix: Json serializer serialized decimal value “6” to “6.0”. Thanks, CorinaCiocanea!
Fix: Json serializer now retains full precision of decimal on roundtrip.
Fix: ETag header was not correctly parsed. Thanks, CorinaCiocanea!
Fix: Parameters with an “=” in the value (like pre-DSTU2 =<=) would become garbled when doing FhirClient.Continue(). Thanks rtaixghealth!
Fix: FhirClient.Meta() operations will use GET and return Meta (not Parameters)

0.90.2

Added support for $translate operations on ConceptMap
Added support for the changed _summary parameter
ArtifactResolver can now resolve ValueSets based on system
The CachedArtifactSource is now thread-safe

0.90.0

Updated the model to be compatible with DSTU2 (1.0.1)
Added support for comments in Json
Fixed a bug where elements called ‘value’ in Json could not have extensions or comments
FhirClient now returns the status code in an OperationException
Bugfixes

0.50.2

Many bug and stability fixes
ReturnFullResource will not only set the Prefer header, but will do a subsequent read if the server ignores the Prefer header.
Client will accept 4xx and 5xx responses when the server does not return an OperationOutcome
Client gives clearer errors when the server returns HTML instead of xml/json
Call signatures for OnBeforeRequest and OnAfterResponse have been changed to give low-level access to body and native .NET objects. OnAfterResponse will now be called even if request failed or if response has parsing errors.
The FhirClient has a full set of new LastXXX properties which return the last received status/resource/body.
Serializers now correctly serialize the contents of a Bundle, even if summary=true

0.20.2

FhirClient updated to handle conditional create/read/update, Preference header
Introduction of TransactionBuilder class to easily compose Bundles containing transactions
Model classes updated to the latest DSTU2 changes
Serialization of extensions back to “DSTU1” style (as agreed in San Antonio)

0.20.1

Added support for async

0.20.0

This is the new DSTU2 release
Supports the new DSTU2 resources and DSTU2 serialization
Uses the new DSTU2 class hierarchy with Base, Resource, DomainResource and Bundle
Further alignment between the Java RM and HAPI
Support for using the DSTU2 Operation framework
Many API improvements, including:

deep compare (IsExactly) and deep copy (DeepCopy)

Collections will be created on-demand, so you can just do patient.Name.Add() without having to set patient.Name to a collection first

Note: support for .NET 4.0 has been dropped, we support .NET 4.5 and PCL 4.5

0.11.1

Project now contains two assemblies: a “lightweight” core assembly (available across all platforms) and an additional library with profile and validation support.
Added an XmlNs class with constants for all relevant xml namespaces used in FHIR
Added JsonXPathNavigator to execute XPath statements over a FHIR-Json based document
Added a new Hl7.Fhir.Specification.Source namespace that contains an ArtifactResolver class to obtain schema files, profiles and valuesets by uri or id. This class will read the provided validation.zip for the core artifacts. For more info see [here](artifacts.html).
Changed FhirUri to use string internally, rather than the Uri class to guarantee round-trips and avoid url normalization issues
All Resources and datatypes now support deep-copying using the DeepCopy() and CopyTo() methods.
FhirClient supports OnBeforeRequest and OnAfterRequest hooks to enable the developer to plug in authentication.
All primitives support IsValidValue() to check input against the constraints for FHIR primitives
Models are up-to-date with FHIR 0.82
And of course we fixed numerous bugs brought forward by the community

0.10.0

There’s a new FhirParser.ParseQueryFromUriParameters() function to parse URL parameters into a FHIR Query resource
The Model classes now implements INotifyPropertyChanged
FhirSerializer supports writing just the summary view of resources
Model elements of type ResourceReference now have an additional ReferencesAttribute (metadata) that indicates the resource names a reference can point to
ModelInfo now has information telling you which FHIR primitive types map to which .NET Model types (this only used to work for complex datatypes and resources before)
We now support both .NET 4.0, .NET 4.5 and Portable Class Libraries 4.5
For .NET 4.5, the FhirClient supports methods with the async signature
All assemblies now have their associated xml documentation files bundled in the NuGet package
Models are up-to-date with FHIR 0.80, DSTU build 2408

0.9.5

This release brings the .NET FHIR library up-to-date with the FHIR DSTU (0.8) version. Additionally, some major changes have been carried out:

There is now some documentation
The FhirClient calls have been changed after feedback of the early users. The most important changes are:

The Read() call now accepts relative and absolute uri’s as a parameter, so you can now do, say, a Read(obs.subject.Reference). This means however that the old calling syntax like Read(“4”) cannot be used anymore, you need to pass at least a correct relative path like Read(“Patient/4”).

Since the FHIR create and update operations don’t return a body anymore, by default the return value of Create() and Update() will be an empty ResourceEntry. If you specify the refresh parameter however, the FHIR client will immediately issue a read, to get the latest updated version from the server.

The Search() signature has been simplified. You can now either use a very basic syntax (like Search(new string[] {“name=john”})), or switch to using the Query resource, which Search() now accepts as a (single) parameter as well.

The validator has been renamed to FhirValidator and now behaves like the standard .NET validators: it validates one level deep only. To validate an object and it’s children (e.g. a Bundle and all its entries and all its nested components and contained resources), specify the new recursive parameter.
The validator will now validate the XHtml according to the restricted FHIR schema, so active content is disallowed.
The library now incorporates the 0.8 version of the Resources. This means that developers using the API’s source distribution need only to compile the project to have all necessary parts, there is no longer a dependency on the Model assembly compiled as part of publication. Note too that the distribution contains the 0.8 resources only (so, no more Appointment resources, etc.).
The library no longer uses the .NET portable class libraries and is based on the normal .NET 4.0 profile. The portable class libraries proved still too unfinished to use comfortably. We’ve fallen back on conditional compiles for Windows Phone support. Cross-platform compilation has not been rigorously tested.
After being updated continuously over the past two years, the FHIR client needed a big refactoring. The code should be readable again.

Before

Is history. If you really want, you can read the SVN and Git logs.