Stream: tooling
Topic: Using arbitrary IG on fhirvalidator.org
Morten Ernebjerg (Aug 26 2021 at 05:59):
I'm recommending fhirvalidator.org to our devs as a super-easy way to test resources being put together in the code, it's really handy :confetti: Ideally, however, we would like to check the resources against our own IG which is published as a FHIR package. As far as I can tell, the online version currently only offers a fixed, limited set of IGs. Is there some way of getting it to pull an arbitrary published FHIR package, similar to using -ig parameter on the CLI tool?
Grahame Grieve (Aug 26 2021 at 06:20):
it offers all IGs that a fully available. IGs authored on simplifier are not available because they are not discoverable. I think
@Mark Iantorno why packages2.fhir.org and not packages.fhir.org?
Morten Ernebjerg (Aug 26 2021 at 07:21):
Does that cover all packages on https://registry.fhir.org ? I tried to search for e.g the de.gecco#1.0.4 package but no match comes up.
Grahame Grieve (Aug 26 2021 at 07:22):
packages2.fhir.org includes all the packages on packages.fhir.org, except the ones from simplifier.
Morten Ernebjerg (Aug 26 2021 at 07:23):
except the ones from simplifier.
OK, that's probably the issue then. Our own package is also published via simplifier. Are the plans to tie in simplifier as well?
Grahame Grieve (Aug 26 2021 at 07:26):
I'd like it to, but it's up to the simplifier team - whether they're going to publish an RSS feed that makes them discoverable. That seems unlikely to me though you can ask.
It would be quicker to change to packages.fhir.org instead on fhirvalidator.org
Morten Ernebjerg (Aug 26 2021 at 07:33):
@Ward Weistra any chance of an RSS feed?
It would be quicker to change to packages.fhir.org instead on fhirvalidator.org
Do you mean use the online simplifier validator at https://simplifier.net/validate ? - yes, you're right, that's of course also an option
Grahame Grieve (Aug 26 2021 at 07:34):
no I mean, fhirvalidator.org is using packages2.fhir.org, but I'd like to see whether it could use packages.fhir.org instead.
Morten Ernebjerg (Aug 26 2021 at 07:36):
:+1:
Ewout Kramer (Aug 26 2021 at 09:37):
@Matthijs van der Wielen
Ewout Kramer (Aug 26 2021 at 09:38):
(@Ward Weistra is on a sabbatical leave)
Mark Iantorno (Aug 26 2021 at 12:34):
I can make it configurable?
Mark Iantorno (Aug 26 2021 at 12:34):
Like a toggle switch?
Mark Iantorno (Aug 26 2021 at 12:35):
is that what you mean?
Grahame Grieve (Aug 26 2021 at 12:44):
well, you could just change it, I think. is there any technical reason why not to?
Mark Iantorno (Aug 26 2021 at 13:28):
No technical reason, but it might be advantageous to provide users with the option, so that if one is down they can still validate?
Grahame Grieve (Aug 26 2021 at 13:29):
maybe, but I don't think packages.fhir.org goes down very much, and users won't understand the choice if we give it to them
Matthijs van der Wielen (Aug 27 2021 at 10:03):
From what I understand from this topic, if we would provide a RSS feed, the packages2.fhir.org would also include all the packages from Simplifier?
What is the reason for having the packages2.fhir.org if all the packages are available on packages.fhir.org to begin with? Is this meant as a back-up?
So far we did not see the point of implementing the RSS feed, because we are the main consumers of the feeds. Causing registry.fhir.org to contain everything found in those feeds. But we will take another look at this.
Grahame Grieve (Aug 27 2021 at 19:22):
packages.fhir.org does not accept all the packages, only specific kinds (the important ones for most people). packages2.fhir.org acts as a functional backup for packages.fhir.org by accepting packages from intermediate versions, and packages to support publishing
But in addition, you are not the only consumers of feeds, even if you are the main consumers; the feeds serve discovery to the whole community for other purposes, but the simplifier packages are all ignored since there's no discovery service. Unless you query simplifier repeatedly
Martijn Harthoorn (Aug 30 2021 at 07:26):
I thought we had https://registry.fhir.org/ for discovery?
Grahame Grieve (Aug 30 2021 at 07:28):
we do, but it discovers different things differently. And it doesn't work for tooling the same way
Grahame Grieve (Aug 30 2021 at 07:28):
in particular, there's no way to be notified of new packages that are released
Martijn Harthoorn (Aug 30 2021 at 07:30):
But an RRS feeds is for exactly that - notification. It's not really meant to do provide a full index, is it?
Grahame Grieve (Aug 30 2021 at 07:31):
no. you'd have to download from the RSS links and do that yourself. Which is what some people want to do. And you can't - to my knowledge - do that from simplifier.
Grahame Grieve (Aug 30 2021 at 07:31):
everything else you can
Martijn Harthoorn (Aug 30 2021 at 07:34):
When working on the FHIR package spec, we left the discovery part out, afaik, partially because
- NPM has a tendency to change their own specs over time.
- We see from other package standards that providing a full index download is not very scalable.
We have implemented package discovery in SImplifier as an API endpoint, so that you can use that in tools, for example in dropdown completion or intellisense.
Martijn Harthoorn (Aug 30 2021 at 07:36):
Martijn Harthoorn (Aug 30 2021 at 07:36):
or packages.simplifier.net/catalog?name=
Grahame Grieve (Aug 30 2021 at 07:41):
so just keep querying that to find new packages? And then once for every package to get all the versions?
Martijn Harthoorn (Aug 30 2021 at 08:14):
We generally use/expose that to find packages yes, not necessarily new.
Martijn Harthoorn (Aug 30 2021 at 08:19):
I am very much open to discuss if we can make this or something similar as part of the spec - or see if we can merge it with the current discovery lists.
Grahame Grieve (Aug 30 2021 at 10:37):
well, it would be good to be able to query for recent versions published. there's no query for that right now
Martijn Harthoorn (Aug 30 2021 at 12:48):
Would it be sufficient to implement a query with a since parameter?
Grahame Grieve (Aug 30 2021 at 12:56):
for versions as well? That's not such a simple addition
Martijn Harthoorn (Aug 30 2021 at 13:01):
Should be possible...
Last updated: Apr 12 2022 at 19:14 UTC
