Stream: ig publishing requirements
Topic: Call today
Lloyd McKenzie (Jul 13 2021 at 19:52):
Friendly remainder :) - 6 Eastern
Oliver Egger (Jul 13 2021 at 20:19):
is it not 5 eastern? at 6 eastern (12 pm here) i'm :sleepy: :sleeping:
Lloyd McKenzie (Jul 13 2021 at 22:19):
Sorry, you're right, it was 5 Eastern. My apologies for creating confusion
Lloyd McKenzie (Jul 27 2021 at 15:16):
Reminder that there will be a call today @ 5 Eastern to continue working through process. (Also want to show the work I've done to change the resource metadata table.)
Jose Costa Teixeira (Jul 27 2021 at 15:19):
can we add to the agenda the questionnaire form rendering? I want to apply it to a few templates OR to the base
Lloyd McKenzie (Jul 27 2021 at 21:04):
Call on now...
Elliot Silver (Jul 27 2021 at 21:05):
Unfortunately I can’t make it today.
Lloyd McKenzie (Jul 27 2021 at 21:05):
@John Moehrke @Eric Haas @ Bob Milius @Elliot Silver @Oliver Egger @Nick George ...
Lloyd McKenzie (Jul 27 2021 at 23:09):
Minutes from our call: https://confluence.hl7.org/display/FHIRI/FHIR+IG+Authoring+Minutes+CC+20210727
Jose Costa Teixeira (Aug 03 2021 at 19:43):
I just realized I have a conflict with the call today
Elliot Silver (Aug 03 2021 at 19:49):
I'll be running errands, but should be able to join intermitmently.
Jose Costa Teixeira (Aug 03 2021 at 19:50):
I wanted to discuss a few things, nothing urgent.
- do accept volunteers to help in building up the guidance-ig? How should we engage? We create a backlog and the volunteers can help?
- We could make a script to deploy a temporary template to our local cache. that couls solve our troubles of deploying and testing templates
Lloyd McKenzie (Aug 03 2021 at 20:17):
I think we certainly accept volunteers to at least make pull requests
Lloyd McKenzie (Aug 10 2021 at 18:43):
Reminder that we'll have our regular call today at 5 Eastern
Lloyd McKenzie (Aug 17 2021 at 20:44):
Call on today - further discussions about process and agreement on most recent template changes
Lloyd McKenzie (Sep 28 2021 at 19:17):
Note that our call will be on today at 5 Eastern as per usual.
Grahame Grieve (Sep 28 2021 at 21:01):
what's the link?
John Moehrke (Sep 28 2021 at 21:03):
http://www.hl7.org/concalls/CallDetails.cfm?concall=56649
John Moehrke (Sep 28 2021 at 21:03):
hasn't been started yet
Jose Costa Teixeira (Oct 05 2021 at 21:03):
is there a call now?
Lloyd McKenzie (Oct 06 2021 at 02:29):
There was - and minutes are here: https://confluence.hl7.org/display/FHIRI/FHIR+IG+Authoring+Minutes+CC+20211005
Jose Costa Teixeira (Oct 12 2021 at 08:03):
For today's call, can we discuss some issues / tools? I'd like to check on this
- changes to the template to support a hapi docker run (I'll make a branch with that change)
- how to use and test a template branch
- how are we with the possibility to reuse content from other IGs
Lloyd McKenzie (Oct 12 2021 at 13:08):
Ok. We also want to finish our review of feedback on process.
Grahame Grieve (Oct 12 2021 at 19:18):
I can't make today's call, but why do templates need a change to support docker? and I'm generally very much against republishing content from other IGs
Jose Costa Teixeira (Oct 12 2021 at 20:18):
the template change to support docker - it's about
a) generating the application.yaml for hapi
b) putting the command line e.g. in the Downloads page so that people can copy-paste it and run that on docker
Grahame Grieve (Oct 12 2021 at 21:20):
is application.yaml a standard?
Jose Costa Teixeira (Oct 12 2021 at 22:05):
you mean if it is a standard, fixed-content file? no.
It is a hapi mechanism (out of the box in hapi, afaik)
Grahame Grieve (Oct 12 2021 at 22:24):
well, publishing it as part of a standard IG has challenges then. How do you want to use it?
Jose Costa Teixeira (Oct 13 2021 at 07:01):
It's the JPA server config file. The IG publisher would generate it so that people can use it to run a pre-configured hapi server
(not sure that is the question you're asking).
Jose Costa Teixeira (Oct 13 2021 at 07:08):
it's not part of our standards, and it's tool-specific. Should the IG produce that? I'd like that, and I don't think a standard can be used there.
Jens Villadsen (Oct 13 2021 at 07:08):
When is the meeting? I'd like to join
Jose Costa Teixeira (Oct 13 2021 at 07:09):
meeting is every tuesday 11 pm your time. I'll invite you for next week
Jose Costa Teixeira (Oct 13 2021 at 07:10):
I think I understand Grahame's point. We do publish OpenAPI because it's a standard. But what do we do with these? Or if I wanted to convert testscripts to Postman format?
Jens Villadsen (Oct 13 2021 at 07:10):
Yep
Jens Villadsen (Oct 13 2021 at 07:10):
Same discussion
Jose Costa Teixeira (Oct 13 2021 at 07:10):
I'd think these should be toggleable features in the IG publisher/template.
Jose Costa Teixeira (Oct 13 2021 at 07:11):
Or we could have plugins for the template.
Jose Costa Teixeira (Oct 13 2021 at 07:11):
I tried that but it didn't work, so the alternative now seems to be: enable the base with a few optional features, let the people switch them on or off.
Jens Villadsen (Oct 13 2021 at 07:12):
There is a 'problem' 'promoting' 3.party tools that are only de facto standards
Jens Villadsen (Oct 13 2021 at 07:13):
So toggling some features sounds like a way forward IMHO
Jens Villadsen (Oct 13 2021 at 07:19):
Docker as well is not a standard
Grahame Grieve (Oct 13 2021 at 10:37):
there's two different questions... generating, and making it part of the spec.
John Moehrke (Oct 13 2021 at 19:42):
I like it as a feature, but it should not be integrated into any IG publication. It is a way to use an IG publication, not the publication itself.
Lloyd McKenzie (Oct 13 2021 at 20:24):
We've talked about having a link to the LHCForms app from Questionnaire. I'm not sure this is all that different...
Grahame Grieve (Oct 13 2021 at 21:02):
that's labelled as an external link. This one wouldn't be, though perhaps we could label it as external anyway, even if it happens to be local? That would clarify that it's a reference of use without being part of the spec
Jens Villadsen (Oct 13 2021 at 21:10):
Is the IG publication toolchain considered part of the FHIR standard?
Grahame Grieve (Oct 13 2021 at 21:27):
no
Grahame Grieve (Oct 13 2021 at 21:27):
though lots of it is dictated by the standard
Jens Villadsen (Oct 13 2021 at 21:28):
so its primarily the 'promotion' thing, right?
Jose Costa Teixeira (Oct 13 2021 at 21:29):
In my view, the IG publisher is a great platform that can and should support plugins. Whether these plugins get the HL7 branding can be a different thing.
Jose Costa Teixeira (Oct 13 2021 at 21:34):
Is the problem that we don't have a good separation between "this is standard content / presented in a standard way" and "these are things you maye be interested in"...?
Jens Villadsen (Oct 13 2021 at 21:34):
how's that?
Jose Costa Teixeira (Oct 13 2021 at 21:35):
I don't know, I'm asking if we need to make that split.
Jens Villadsen (Oct 13 2021 at 21:36):
promoting using docker is promoting a de facto standard - there is little/no harm in that, IMHO
Jens Villadsen (Oct 13 2021 at 21:36):
i consider that almost the same as using plantuml
Jens Villadsen (Oct 13 2021 at 21:38):
exemplifying a running FHIR server using docker and eg. HAPI FHIR is a bit more complicated
Jens Villadsen (Oct 13 2021 at 21:44):
in terms of 'promoting', IMHO
Grahame Grieve (Oct 13 2021 at 22:11):
as @Lloyd McKenzie points out, we're happy to add implementer collateral that's not part of the spec. We can add this for more than one server, so that's not a problem. It just can't be part of the spec.
Jose Costa Teixeira (Oct 13 2021 at 22:13):
should we make clear somehow that this is not part of the spec?
Lloyd McKenzie (Oct 14 2021 at 03:01):
Primarily in the blob of text prior to the link (which should also set expectations about what the auto-generated server will and won't do). Also, I'm not really understanding how there can really be a single docker for an IG - wouldn't there be one for each CapabilityStatement (or at least each CapabilityStatement that had server capabilities defined)?
Jens Villadsen (Oct 14 2021 at 08:29):
@Lloyd McKenzie for now, yes. The capability statement is currently autogenerated by HAPI so with the current setup, it would be the 'joined set' of capabilities that will be exposed
Jens Villadsen (Oct 14 2021 at 08:30):
An alternative approach would be a docker-compose setup
Jose Costa Teixeira (Oct 14 2021 at 10:23):
I'd like to put this on a base template branch so that we can iterate from a first draft. Is that ok?
Lloyd McKenzie (Oct 14 2021 at 12:23):
At least in theory, you might have CapabilityStatements where one server is required to have a function and another is prohibited from having it, so squishing everything into one server seems problematic to me...
Jose Costa Teixeira (Oct 14 2021 at 13:02):
Yes, there arequestions and challenges. By making a branch, I definitely don't mean discussion is over, just to get this started.
Jose Costa Teixeira (Oct 14 2021 at 13:02):
Perhaps we have to indeed pick the CapStatements for which this to be is produced (I recalll some preliminary discussions there but no conclusions).
Jens Villadsen (Oct 14 2021 at 18:21):
I'd favor getting some feedback using what @Jose Costa Teixeira has already built. If you are in a need of having to host multiple CapStmt's, then just instantiate more containers - remember - they can be used for test purposes and are not qualified for much more than that
Jens Villadsen (Oct 14 2021 at 18:23):
Let's get this setup out there and hear if it is useful to others.
Jens Villadsen (Oct 14 2021 at 18:24):
We could even retag the container and republish it under a specific tag to see how often the feature is used ;)
Jose Costa Teixeira (Nov 14 2021 at 19:05):
For our next call, before the front matter discussions, can we address the "server launch" thing? To see if we should invite the central europeans that have a normal sleep pattern.
Lloyd McKenzie (Nov 14 2021 at 19:39):
Sure. Though we'll also have some TSC reps showing up I believe.
Eric Haas (Nov 15 2021 at 16:36):
what is server launch?
Jose Costa Teixeira (Nov 15 2021 at 17:01):
it's when the IG creates a configuration file that can be used to deploy a server that implements that IG (of whatever part of the IG can be implemented automatically - CapStatements, profiles, instances, terminology)
Jose Costa Teixeira (Nov 16 2021 at 18:59):
Do we have an agenda for today?
Lloyd McKenzie (Nov 16 2021 at 19:19):
I think we'll have TSC folks on the call, so I guess bring them up to speed, then tackle front matter, approve the example rendering enhancements Grahame has already made?, discussion of 'pure differential' and whether we want to punt it to FHIR-I and - if we get through all of that, perhaps a discussion of front matter/how to support publishing 'special' logical models
Lloyd McKenzie (Nov 16 2021 at 19:20):
Order of the above we can figure out based on who's on the call and relative priorities.
Elliot Silver (Nov 16 2021 at 19:24):
I wouldn't mind a discussion of rendering contained resources.
Lloyd McKenzie (Nov 16 2021 at 19:28):
That would be good. I'd like to not make them separate pages if we can - just incorporate the narrative blocks for each contained resource onto the narrative page.
Grahame Grieve (Nov 16 2021 at 19:39):
but it's not just narrative blocks. There's resource type specific things that we do and add to the page
Grahame Grieve (Nov 16 2021 at 19:39):
e.g. value set expansions
Jose Costa Teixeira (Nov 16 2021 at 19:44):
Right. I have a few priority items too, but I'm happy if we prioritize the TSC reps catch-up and the changes that are alredy implemented.
Jose Costa Teixeira (Nov 16 2021 at 19:45):
So no server launch discussion today - that's a pity but then we don't need to ask @Jens Villadsen to join
Jose Costa Teixeira (Nov 16 2021 at 19:45):
Discussion on rendering contained resources - is there a gh issue for that?
Elliot Silver (Nov 16 2021 at 20:21):
https://github.com/HL7/fhir-ig-publisher/issues/228 is where I entered my issues last year.
Jose Costa Teixeira (Nov 16 2021 at 20:28):
Thanks. We should perhaps try to adjust the priorities of the issues we think we can discuss first
Jens Villadsen (Nov 16 2021 at 20:50):
Ill focus on nordic and EU stuff then
Jose Costa Teixeira (Nov 16 2021 at 23:20):
Calling dibs on agenda topics -my top 3 today as they would unblock a set of nice things - besides the LM instance:
- allow the release-update process to skip the manual y/n prompt
- allow importing of other artifacts into an IG - what would be the impact on packages?
- Server launch
Jose Costa Teixeira (Nov 18 2021 at 20:18):
I made a PR for #1 above - I tested and it meets my need,
But I do not know if the code is following any good coding practices in Java
Jose Costa Teixeira (Dec 21 2021 at 18:35):
Is there a call today?
Lloyd McKenzie (Dec 22 2021 at 15:21):
no
John Moehrke (Dec 22 2021 at 15:27):
thanks for that timely response... ;-)
Lloyd McKenzie (Jan 04 2022 at 21:41):
We will have our call today
John Moehrke (Jan 04 2022 at 22:03):
ready when you are
Jose Costa Teixeira (Feb 01 2022 at 20:29):
is there a call today?
Elliot Silver (Feb 01 2022 at 21:14):
I assume so.
Lloyd McKenzie (Feb 01 2022 at 21:16):
Yup
Lloyd McKenzie (Feb 01 2022 at 21:16):
In 45 min.
Grahame Grieve (Feb 01 2022 at 21:23):
I'll miss it today
Lloyd McKenzie (Feb 01 2022 at 23:30):
We spent most of our time on this issue: https://jira.hl7.org/browse/FHIR-20385
We have a proposed resolution, however parts require broader review so will hopefully take it up w/ FHIR-I on Monday.
Last updated: Apr 12 2022 at 19:14 UTC
