FHIR Chat · IG or should I say IGs · Da Vinci

Stream: Da Vinci

Topic: IG or should I say IGs

view this post on Zulip Eric Haas (Jul 19 2018 at 19:22):

@Bryn Rhodes @Lloyd McKenzie @Viet Nguyen As discussed in an email, I think we need 3 repos for three IG.s overarching guide with narrative and R4 artifacts Guide and STU3 artifacts Guide. The existing tooling will only support a single version. As I understand it, the npm-name is the same across versions but what about the overarching guide. how-to-publish-two-version-IGs.jpg

view this post on Zulip Lloyd McKenzie (Jul 19 2018 at 19:38):

I'm not sure that the npm-name can be the same - because we want the version numbers of the IGs to be the same too. And I think NPM-name and version have to be unique. (And if we're going to vary one or the other, I'd rather vary the NPM-name.) I believe we can maintain a single repository though.

view this post on Zulip Eric Haas (Jul 19 2018 at 19:47):

I don't think autopub supports (>1 ig)/(per repo).

view this post on Zulip Lloyd McKenzie (Jul 19 2018 at 19:54):

Yeah, that's true. We'll have to play with that a bit. My objective is definitely one repo. It's much better if you need to make a change that affects multiple versions to be able to apply it in a single commit.

view this post on Zulip Bryn Rhodes (Jul 19 2018 at 20:02):

I wonder if what we should do for this first pass is only produce an STU3 version and get to R4 after ballot? R4 is already a moving target that's going to be hard to hit.

view this post on Zulip Eric Haas (Jul 19 2018 at 20:05):

to clarify the npm-name is the same across versions. e.g..

  • hl7.fhir.us.core-1.0.1
  • hl7.fhir.us.core-1.1.0

so it would be

  • hl7.fhir.davinci.deqm-3.0.0?

and

  • hl7.fhir.davinci.deqm-4.0.0?

view this post on Zulip Eric Haas (Jul 19 2018 at 20:08):

I agree with you Lloyd on the one repo. I think it is better to work around the autopub.

view this post on Zulip Bryn Rhodes (Jul 19 2018 at 20:15):

Yes, I agree with one repo too, I'm saying that we should build the version 3, and then build the version 4 as a next step.

view this post on Zulip Eric Haas (Jul 19 2018 at 20:19):

@Bryn I agree with your approach, but that decision was not ours :-(

view this post on Zulip Lloyd McKenzie (Jul 19 2018 at 20:49):

1.0.1 and 1.1.0 in your example aren't FHIR versions, they're IG versions. We want a single IG version that includes artifacts from multiple FHIR versions. But the NPM mechanism doesn't (currently - or anticipated ever) support multiple resource versions in a single package.

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -