Skip to content

Releases: FirelyTeam/firely-net-sdk

3.2.0 for R4B (release 20210504)

04 May 13:58
Compare
Choose a tag to compare

Description

⚠️ New release 4B, edition march 2021 (https://www.hl7.org/fhir/2021Mar/). This is still an experimental version.

Known issues

  • There are no search parameters. The parameters that were provided are experimental and will not be generated for the SDK
  • StructureDefinition PrimitiveType was not provided. Copied the one from R4 for this release
  • The files profiles-types.xml, profile-resources.xml and profiles-others.xml are corrected because:
    • Extension http://hl7.org/fhir/StructureDefinition/structuredefinition-fhir-type was incorrect: valueUri instead of valueUrl
    • Extension http://hl7.org/fhir/build/StructureDefinition/definition is not an existing extension
  • fhr-single.xsd has been corrected, because of missing elements and incorrect elements (therapy[x])
  • examples.zip has been corrected
  • examples-json.zip has been corrected

3.2.0 for R4 (release 20210504)

04 May 12:42
Compare
Choose a tag to compare

Changes:

  • #1701: Moved another set of classes to Common
  • #1690: FhirClient: handle prefer operation outcome in resource response
  • #1689: Correct construction of Terminology service output
  • #1685: Made some extensions of ElementDefinitionNavigator public (for R4)
  • #1683: Reorganize slicing helper functions (for R4)

This list of changes was auto generated.

3.1.0 for STU3 (release 20210401)

01 Apr 15:49
Compare
Choose a tag to compare

Changed behavior

⚠️ As part of issue #1666 we have implemented a better solution for the FhirPath function htmlChecks(). That means for users who are using this FhirPath function that the outcome can be different from previous versions. We are more stricter and closer to the official FhirPath standard. Because this function htmlChecks() is also used in some invariants of the official FHIR standard, there could be an other and more correct outcome as well. Invariants txt-1 and txt-2 of Narrative are using this htmlChecks().
For example, using a <div> element without the namespace xmlns=http://www.w3.org/1999/xhtml will now end up in an error during validation.

Changes:

  • #1676: Optional include of mandatory elements to the list of provided elements during serialization
  • #1663: Input parameters for TerminologyService are checked for duplicates
  • #1672: ScopedNode: AtResource can also be determined from IResourceTypeSupplier
  • #1673: Add support for exists slicing
  • #1671: Can now use a discriminator to walk into a complex extension (for R3)
  • #1662: Support relative URLs when parsing HttpResponseMessage to EntryResponse
  • #1666: Add memberOf function to the FP symbol table
  • #1664: TryGetFhirReleaseFromCorePackageName now returns correct result
  • #1665: Terminology unit tests are not run in Devops anymore
  • #1647: New Powershell scripts to create and finish a release
See More
  • #1644: Updated Readme.md to document breaking changes more clearly

This list of changes was auto generated.

3.1.0 for R5 (release 20210401)

01 Apr 15:54
Compare
Choose a tag to compare

Changed behavior

⚠️ As part of issue #1666 we have implemented a better solution for the FhirPath function htmlChecks(). That means for users who are using this FhirPath function that the outcome can be different from previous versions. We are more stricter and closer to the official FhirPath standard. Because this function htmlChecks() is also used in some invariants of the official FHIR standard, there could be an other and more correct outcome as well. Invariants txt-1 and txt-2 of Narrative are using this htmlChecks().
For example, using a <div> element without the namespace xmlns=http://www.w3.org/1999/xhtml will now end up in an error during validation.

Changes:

  • #1676: Optional include of mandatory elements to the list of provided elements during serialization
  • #1663: Input parameters for TerminologyService are checked for duplicates
  • #1672: ScopedNode: AtResource can also be determined from IResourceTypeSupplier
  • #1673: Add support for exists slicing
  • #1671: Can now use a discriminator to walk into a complex extension (for R3)
  • #1662: Support relative URLs when parsing HttpResponseMessage to EntryResponse
  • #1666: Add memberOf function to the FP symbol table
  • #1664: TryGetFhirReleaseFromCorePackageName now returns correct result
  • #1665: Terminology unit tests are not run in Devops anymore
See More
  • #1647: New Powershell scripts to create and finish a release
  • #1644: Updated Readme.md to document breaking changes more clearly

This list of changes was auto generated.

3.1.0 for R4 (release 20210401)

01 Apr 15:50
Compare
Choose a tag to compare

Changed behavior

⚠️ As part of issue #1666 we have implemented a better solution for the FhirPath function htmlChecks(). That means for users who are using this FhirPath function that the outcome can be different from previous versions. We are more stricter and closer to the official FhirPath standard. Because this function htmlChecks() is also used in some invariants of the official FHIR standard, there could be an other and more correct outcome as well. Invariants txt-1 and txt-2 of Narrative are using this htmlChecks().
For example, using a <div> element without the namespace xmlns=http://www.w3.org/1999/xhtml will now end up in an error during validation.

Changes:

  • #1678: Update develop-r4 with develop-stu3 for release 3.1
  • #1676: Optional include of mandatory elements to the list of provided elements during serialization
  • #1663: Input parameters for TerminologyService are checked for duplicates
  • #1672: ScopedNode: AtResource can also be determined from IResourceTypeSupplier
  • #1673: Add support for exists slicing
  • #1671: Can now use a discriminator to walk into a complex extension (for R3)
  • #1662: Support relative URLs when parsing HttpResponseMessage to EntryResponse
  • #1666: Add memberOf function to the FP symbol table
  • #1664: TryGetFhirReleaseFromCorePackageName now returns correct result
  • #1665: Terminology unit tests are not run in Devops anymore
See More
  • #1647: New Powershell scripts to create and finish a release
  • #1644: Updated Readme.md to document breaking changes more clearly

This list of changes was auto generated.

3.0.0 for STU3 (release 20210225)

25 Feb 16:57
Compare
Choose a tag to compare

A major release, because we introduced some small breaking changes. For a lot of users of this SDK this upgrade to version 3.0 will be easy and no changes are required. For a small group of users there are some changes to be made. In this document you can see which breaking changes we have made for version 3.0.

On the other hand this release brings some relief for users who are using multiple versions of the SDK in one project. Because we have moved some basic classes to the common library, like OperationOutcome and ResourceIdentity, it will be much easier to maintain the code for those users.

Changes:

  • #1641: Adding extra GitHubRelease task
  • #1640: R3: Null reference exception solved for FP Resolve() on empty collection
  • #1637: R3: moved some classes to common
  • #1628: Add FHIR Release utilities and move to C# 9.0
  • #1629: Fix DebuggingDisplays of ResourceIdentity
  • #1624: Devops/create parallel jobs
  • #1615: feature/1612: Moved more types to common
  • #1623: Fix/1606: TypedElementOnSourceNode logical model data type (for STU3)
  • #1606: TypedElementOnSourceNode throws StructuralTypeException on .value for "complex" logical model data type
  • #1613: Fix Verification of FHIR version of FhirClient
  • #1602: Update docs link in readme.md
  • #1604: Added nuget downloads info to readme
  • #1611: LocalTerminologyService: Adding ConfigureAwait(false) at async calls

This list of changes was auto generated.

3.0.0 for R5 (release 20210225)

25 Feb 16:58
Compare
Choose a tag to compare

A major release, because we introduced some small breaking changes. For a lot of users of this SDK this upgrade to version 3.0 will be easy and no changes are required. For a small group of users there are some changes to be made. In this document you can see which breaking changes we have made for version 3.0.

On the other hand this release brings some relief for users who are using multiple versions of the SDK in one project. Because we have moved some basic classes to the common library, like OperationOutcome and ResourceIdentity, it will be much easier to maintain the code for those users.

Changes:

  • #1642: Update R5 with R4 changes
  • #1638: Feature/update r4 with r3 changes
  • #1641: Adding extra GitHubRelease task
  • #1640: R3: Null reference exception solved for FP Resolve() on empty collection
  • #1639: R4: Use a better validation regex for strings
  • #1637: R3: moved some classes to common
  • #1628: Add FHIR Release utilities and move to C# 9.0
  • #1629: Fix DebuggingDisplays of ResourceIdentity
  • #1624: Devops/create parallel jobs
  • #1627: Forward changes from R4 to R5
See More
  • #1626: Feature 1612: Move more types to common (R4)
  • #1625: Merge R3 changes into R4
  • #1615: feature/1612: Moved more types to common
  • #1623: Fix/1606: TypedElementOnSourceNode logical model data type (for STU3)
  • #1606: TypedElementOnSourceNode throws StructuralTypeException on .value for "complex" logical model data type
  • #1613: Fix Verification of FHIR version of FhirClient
  • #1602: Update docs link in readme.md
  • #1604: Added nuget downloads info to readme
  • #1611: LocalTerminologyService: Adding ConfigureAwait(false) at async calls

This list of changes was auto generated.

3.0.0 for R4 (release 20210225)

25 Feb 16:58
Compare
Choose a tag to compare

A major release, because we introduced some small breaking changes. For a lot of users of this SDK this upgrade to version 3.0 will be easy and no changes are required. For a small group of users there are some changes to be made. In this document you can see which breaking changes we have made for version 3.0.

On the other hand this release brings some relief for users who are using multiple versions of the SDK in one project. Because we have moved some basic classes to the common library, like OperationOutcome and ResourceIdentity, it will be much easier to maintain the code for those users.

Changes:

  • #1638: Feature/update r4 with r3 changes
  • #1641: Adding extra GitHubRelease task
  • #1640: R3: Null reference exception solved for FP Resolve() on empty collection
  • #1639: R4: Use a better validation regex for strings
  • #1637: R3: moved some classes to common
  • #1628: Add FHIR Release utilities and move to C# 9.0
  • #1629: Fix DebuggingDisplays of ResourceIdentity
  • #1624: Devops/create parallel jobs
  • #1626: Feature 1612: Move more types to common (R4)
  • #1625: Merge R3 changes into R4
See More
  • #1615: feature/1612: Moved more types to common
  • #1623: Fix/1606: TypedElementOnSourceNode logical model data type (for STU3)
  • #1606: TypedElementOnSourceNode throws StructuralTypeException on .value for "complex" logical model data type
  • #1613: Fix Verification of FHIR version of FhirClient
  • #1602: Update docs link in readme.md
  • #1604: Added nuget downloads info to readme
  • #1611: LocalTerminologyService: Adding ConfigureAwait(false) at async calls

This list of changes was auto generated.

2.0.3 for STU3 (release 2020126) - HOTFIX

26 Jan 16:17
Compare
Choose a tag to compare

This is a hotfix for solving issue #1605.

We are not throwing an exception anymore during an Equals of Quantity.

Bugfixes

  • #1605 Cannot select quantities with different units within a single FHIRPath select

2.0.3 for R5 (release 2020126) - HOTFIX

26 Jan 16:18
Compare
Choose a tag to compare

This is a hotfix for solving issue #1605.

We are not throwing an exception anymore during an Equals of Quantity.

Bugfixes

  • #1605 Cannot select quantities with different units within a single FHIRPath select