Stream: implementers
Topic: Canonical URL + profile hosting
Matthew Koch (Jun 19 2019 at 16:50):
If we are creating R4 profiles and hosting them on Simplifier.net, could we use simplifier.net in the url attribute of the profiles? Secondly, are R4 profiles going to be uploaded to registry.fhir.org at some point in the future? Right now it only looks like STU3 profiles are there.
Vadim Peretokin (Jun 19 2019 at 17:11):
You can use simplifier.net as part of the canonical URL, yep. Though the convention is to use some url related to your organisation
Registry - right now it only searches STU3 content, that would be a question for Grahame
Matthew Koch (Jun 19 2019 at 17:14):
I had thought that it was important for the URLS to resolve, that's why Iw anted to use something where if someone popped them into a browser they'd work. The profiles I am referring to are the output of a consortium. Is it acceptable to have "fake" URLS that just uniquely identify the profile? If so, that's a lot easier...
Lloyd McKenzie (Jun 19 2019 at 17:28):
Good practice is for them to resolve, but that's not mandatory. (Even if they do 'resolve', there's no guarantee they'll resolve 24x7 for every system that tries.)
Grahame Grieve (Jun 19 2019 at 22:12):
I can't upload R4 stuff to the simplifier right now - at least, that's what I was told. Getting the registry sorted out is on my list of things to do, but it's been waiting for us to have a reproducible IG publication framework
Vadim Peretokin (Jun 20 2019 at 02:10):
There's also this: https://simplifier.net/resolve
Alexander Zautke (Jun 20 2019 at 09:31):
CC: @Martijn Harthoorn
Michel Rutten (Jun 20 2019 at 10:21):
Hi @Matthew Koch, yes, you can publish profiles with a canonical url that is based on the simplifier domain. However in general, FHIR strongly recommends to use a publication url based on a domain of your organization that is under your control. Simplifier allows you to "claim" a domain name; the platform will then only allow members of the owning organization to publish on that specific domain.
Canonical urls must be unique, but FHIR does not require them to actually resolve. However authors are encouraged to serve a web page that describes the associated profile (similar to the FHIR spec pages that describe the core resource definitions).
Michel Rutten (Jun 20 2019 at 10:25):
@Grahame Grieve Simplifier already accepts R4 profiles & NPM packages, if uploaded manually through the website. We still need to update the FHIR API endpoint to support R4 (soon); this will also allow Simplifier to perform snapshot generation & validation of R4 profiles.
Martijn Harthoorn (Jun 20 2019 at 12:29):
Correct. Simplifier uploads R4 resources, zips and FHIR packages.
Martijn Harthoorn (Jun 20 2019 at 12:30):
And Snapshot-Generation and Validation via the UI is possible.
Grahame Grieve (Jun 20 2019 at 19:26):
I've added this to my todo list
Natasha Singh (Jun 24 2019 at 20:27):
@Michel Rutten hey michael, I'm sorry if this is a repeat question but I just want to make sure I understand correctly. I want to programmatically update a package under my project (R4) on simplifier. I think you mentioned earlier that uploading via an API endpoint is not yet supported in R4 projects? Is that correct?
Vadim Peretokin (Jun 24 2019 at 20:28):
That's right, not possible just yet
Natasha Singh (Jun 24 2019 at 20:31):
Ok @Vadim Peretokin , it looks like this is supported in STU3 via the project ZIP endpoint? Is that correct or is there a way to update just the package within a project rather than the entire project?
Vadim Peretokin (Jun 24 2019 at 20:33):
I don't believe there's a package management API just yet, but @Martijn Harthoorn can correct me on that tomorrow if that's not the case :)
We're definitely looking into this. I take it you'd like to publish as part of CI?
Natasha Singh (Jun 24 2019 at 20:35):
Yes @Vadim Peretokin , I'd like to host my packages in a GH repo, run validation on every commit (on every branch), and then upload/update a package on PR approval/merge into my master branch
Natasha Singh (Jun 24 2019 at 20:35):
I was expecting I could push packages via Torinox, but it looks like thats not supported yet
Martijn Harthoorn (Jun 25 2019 at 08:21):
Correct: we did not open up the package registry in Simplifier for direct upload yet, because we need to have some quality control process in between. But we are working on that.
You can definitely upload via the zip endpoint to any R4 project and create a package from there.
Natasha Singh (Jul 02 2019 at 16:52):
I don't believe there's a package management API just yet, but Martijn Harthoorn can correct me on that tomorrow if that's not the case :)
We're definitely looking into this. I take it you'd like to publish as part of CI?
@Martijn Harthoorn @Sebastiaan Raap Perhaps the answer to this question is part of ^, but is it possible to programmatically via an API call delete files in my Simplifier Project instead of using the UI (Settings > Delete)?
Martijn Harthoorn (Jul 03 2019 at 09:19):
Yes, if you know the identifiers of your resources, you can use the FHIR API endpoint to delete files programmatically. And we are working very hard to give you more options.
And ofcourse our enterprise users already have that option using github webhook.
Last updated: Apr 12 2022 at 19:14 UTC
