IE (Ireland) Core Implementation Guide
1.0.0-ballot - Ballot Ireland flag

Publication Build: This will be filled in by the publication tooling

Changes Between Versions

Page standards status: Informative

Introduction

With each major version of FHIR, the core data models have changed. The FHIR core specification provides a base resource differential to help implementers navigate version changes. However, there are additional considerations for the user and developer experience when transitioning from FHIR Version DSTU2 to FHIR R4. Similarly, IE Core undergoes annual updates, which are documented on the Future of IE Core page. Each update to a new version of IE Core changes the IE Core Profiles and conformance expectations. The following guidance on this page is provided to ensure a smoother upgrade path. It reflects non-normative best practices established at the time of publication.

Versioning of IE Core

IE Core undergoes annual updates with new guidance, requirements, profiles, and changes to existing content. The Directory of published versions lists the publication history with links to each version of IE Core. The Change Log documents the changes across the versions of IE Core.

Work is underway to identify corrections in subsequent versions as "patches" to prior versions for certification.

No Guarantee that Resource IDs are Preserved

In some FHIR servers, the identifier of the underlying clinical data is not maintained across FHIR versions. Therefore, client applications must plan on deduplication methods that rely on something other than a common identifier across FHIR versions.

  • Servers SHOULD maintain a stable common identifier for a resource across versions.

Authorization Across Versions

  • Separate authorization is required
    • There is no expectation that DSTU2 authorizations will work on R4 endpoints, and reauthorization is required when migrating between versions.
      • Maintaining the same auth server for both endpoints so that the refresh token is valid for both DSTU2 and the R4 endpoint may be possible but not in scope.
  • The new endpoint will bring additional/changed resource types and added scopes