FHIR Chat · server conformance resource importer · implementers

Stream: implementers

Topic: server conformance resource importer


view this post on Zulip Brian Postlethwaite (Nov 02 2018 at 02:44):

I've been implementing the ability to load in a package (of conformance resources) onto my server via an administrative operation and was wondering if others have tried this too.
The first real issue that I've come across was that if I permit the retention of the Resource.Id fields in the package, there is a good chance that these will cause conflicts, overwriting a resource that used that ID elsewhere - in my case was FhirCore - AuBase - AuPD, and had the Id reused at each of the levels in various ways.
Thinking that I'll just want to stop the re-use of IDs bringing them in.

view this post on Zulip Brian Postlethwaite (Nov 02 2018 at 03:57):

I'd advise others to not use the provided Ids, unless you know what you're doing - in my server I'm now doing a prefix during the import - but will be controlled use anyway - and typically only used to move conformances from one system to another (packaging configuration distribution)

view this post on Zulip Vadim Peretokin (Nov 02 2018 at 09:31):

Vonk already allows importing resources on a separate administrative endpoint - and it forbids from two different resources having the same canonical url (http://docs.simplifier.net/vonk/features/conformanceresources.html#conformance)

view this post on Zulip Vadim Peretokin (Nov 02 2018 at 09:31):

That's what matters in the end, no? Not the .id

view this post on Zulip Michel Rutten (Nov 02 2018 at 10:58):

Resource ids MUST be unique. A FHIR server could store multiple StructureDefinitions that all share a common canonical url (for example Simplifier). However each instance must have a unique resource id.

view this post on Zulip Lloyd McKenzie (Nov 02 2018 at 14:54):

Canonical URLs can be dupicate. It's totally possible for a server to host multiple business versions of the same value set. They'll have the same canonical URL but different version elements. They'll also have to have different id elements - which could be pretty much anything.

view this post on Zulip Brian Postlethwaite (Nov 03 2018 at 03:45):

Yes, my problem wasn't ending up with duplicates, it was with over-writing resources.

view this post on Zulip Brian Postlethwaite (Nov 03 2018 at 03:45):

(As 2 guides used the same Id for different value sets)

view this post on Zulip Christiaan Knaap (Dec 17 2018 at 11:12):

Just checked: we report a conflict if you put the same canonical with a different id, but not the other way around. Should check that as well. In general I think it is fairly safe to ignore the provided id's an assign your own server-specific id's.


Last updated: Apr 12 2022 at 19:14 UTC