Stream: dotnet
Topic: Fhir Version
Clint Moran (Aug 29 2019 at 15:42):
Hello! My organization maintain a patient education app that launches within EMRs (EPIC, Cerner) and we have been using the .net FHIR libraries for authentication, patient context gathering and document write-back. The issue we are having now is that our app is being launched from two different vendors that are wanting to use two different FHIR specs. One is on STU3 and the other supports DSTU2 or R4. If I update our libraries to use the Hl7.Fhir.R4 version will that work with DSTU2, STU3, and R4 clients? Thanks!
Michele Mottini (Aug 29 2019 at 16:00):
No - the R4 version works only with R4 server. There is https://www.nuget.org/packages/CareEvolution.Fhir.Core/ that supports multiple version
Michel Rutten (Aug 29 2019 at 16:00):
Hi @Clint Moran, the .NET API has separate branches & releases for DSTU2, STU3 and R4. Common logic (e.g. FhirPath compiler) has been split of to separate components, independent of the FHIR version. However the core libraries are version-specific.
It is possible to consume multiple assembly versions simultaneously from a single project using assembly aliasing. This allows you to create a FHIR client that supports multiple FHIR versions. However you will need to write some conditional logic, depending on the runtime FHIR version.
Michel Rutten (Aug 29 2019 at 16:01):
Clint Moran (Aug 29 2019 at 16:25):
Thanks! My initial plan was to create a web API per FHIR specification as I wanted to avoid any reflection or assembly wizardry but spinning up three web APIs felt unnecessary. Thanks again for the info!
Last updated: Apr 12 2022 at 19:14 UTC
