Stream: conformance
Topic: registry.fhir.org
Grahame Grieve (Oct 15 2019 at 11:01):
Looking at the content on registry.fhir.org, I don't see Jurisdiction populated very often. But I think it should always be populated. @Ward Weistra does simplifier allow users to edit jurisdiction? can it make it required before posting to registry.fhir.org?
Grahame Grieve (Oct 15 2019 at 12:45):
Also, the registry endpoint is R3.... how does multiple versions work on it now?
Ward Weistra (Oct 15 2019 at 13:24):
Indeed, jurisdiction seems to be empty on most results. It seems to be 0..* on most (all?) resources: https://www.hl7.org/fhir/structuredefinition-definitions.html#StructureDefinition.jurisdiction. But you're suggesting an extra level of quality checks before qualifying for registry.fhir.org, right?
That's a great idea and something we would love to build. Bulk validation is something on the near term roadmap, adding custom validation rules (I hear suggestions of profile on StructureDefinition ect. or FHIR Path statements) would be a great addition. Also for checking organization specific rules.
Simplifier doesn't have an edit field for it, but if you include it as part of the uploaded resources it will be passed on to registry.fhir.org.
Grahame Grieve (Oct 15 2019 at 13:44):
I would simplifier to have a field so it can be edited please, and I would like registry.fhir.org to require it. That raises the question of what to do about existing content...
Ward Weistra (Oct 15 2019 at 13:48):
On the API endpoint, you can get R4 resources by adding the headerAccept: application/fhir+json; fhirVersion=4.0.
Current Vonk has multiple versions on the same endpoint, with STU3 as default: http://docs.simplifier.net/vonk/features/multiversion.html
Ward Weistra (Oct 15 2019 at 13:59):
It should be noted that via the UI only STU3 resources are returned, since it calls to the FHIR endpoint without fhirVersion header and thus gets the default. A clear action item to add to the registry upgrade RFP.
Grahame Grieve (Oct 15 2019 at 15:54):
You get the same set of resources with that header? Or different resources? What about r2?
Ward Weistra (Oct 16 2019 at 09:44):
You'll get different resources:
GET https://registry-api.fhir.org/open/metadataorGET https://registry-api.fhir.org/open/Patient?_count=20orGET https://registry-api.fhir.org/open/Patient/073e9dc8-a0f4-46cf-9263-33a2c02c5910with headerAccept:application/fhir+jsonorAccept:application/fhir+json; fhirVersion=3.0will talk to the Vonk 3.0 endpoint on Simplifier and only return FHIR STU3 resources (it will also tell you on the last one it only has that resource for another FHIR version)- The same calls with header
Accept:application/fhir+json; fhirVersion=4.0will talk to the Vonk R4 endpoint and only return FHIR R4 resources
The upcoming version of Vonk will also support having separate endpoints for this (no need to use the header anymore) and setting what the default FHIR version should be.
To my understanding registry.fhir.org never had a DSTU2 endpoint, it used to only talk to the STU3 Vonk endpoint on Simplifier. The current Vonk version that supports multiple FHIR versions in one server also only supports STU3 and up.
I would support configuring the endpoint such that there's dedicated endpoints for different FHIR versions, like Simplifier's current https://fhir.simplifier.net/r3 and https://fhir.simplifier.net/r4. And of course being able to indicate FHIR version when searching in the UI of registry.fhir.org.
Grahame Grieve (Oct 16 2019 at 10:48):
We have a few R2 guides and profiles. Is it hard to add R2 support?
Ward Weistra (Oct 16 2019 at 11:18):
From what I hear that is probably an expensive addition. Spark did have an DSTU2 version, but Vonk started at STU3. Are those R2 resources still widely used, or is it more out of completeness?
Grahame Grieve (Oct 16 2019 at 11:19):
..Argonaut....
Ward Weistra (Oct 16 2019 at 12:14):
Fair point, the Argonaut Data Query Implementation Guide, which is used in Apple HealthKit...
While adoption will take a while, I read at least the next version of that IG (rolled into US-Core) is coming out soon? I hope users trying to find things via the Registry (generally new users who start implementing FHIR?) will be looking for the most recent resources to base their work on.
Grahame Grieve (Oct 16 2019 at 12:36):
well, there won't be more R2 guides, I'm pretty sure about that
Last updated: Apr 12 2022 at 19:14 UTC
