Stream: Da+Vinci+PDex+Plan-Net
Topic: Outdated FHIR Registry Package
Fred Harmon (Oct 30 2020 at 13:55):
Does anyone know when https://registry.fhir.org/package/hl7.fhir.us.davinci-pdex-plan-net%7C0.1.0 will be updated with a more recent build? The version that is out there still references dependencies for "hl7.fhir.core": "4.0.0" when the latest in Git Hub reference dependencies for "hl7.fhir.r4.core": "4.0.1", "hl7.fhir.us.core": "3.1.0" .
I mainly ask because the software I import these profile packages into uses the exact output from the FHIR registry and I'm not sure how to turn the FSH files on Github into that myself.
If anyone here has a way to get the Registry update, that would be extremely helpful. I do realize this isn't a finalized spec, but having something more up to date on the registry would be helpful.
Thanks
Fred
Saul Kravitz (Oct 30 2020 at 15:52):
I would hope that would happen when v1.0.0 is published, speedily in our day.
Fred Harmon (Nov 02 2020 at 18:59):
Thanks @Saul Kravitz . I was trying to find agenda or meeting schedule so I could figure out when the 1.0.0 version may be published by haven't had luck. Could you help with pointing me in the right direction? Thanks.
Saul Kravitz (Nov 02 2020 at 19:31):
We are getting very close. It is dependent on HL7 processes that we don't control. I hope it will be out before Thanksgiving.
Fred Harmon (Nov 03 2020 at 12:57):
Oh that is fantastic news Saul. Thanks.
Fred Harmon (Nov 25 2020 at 14:25):
@Saul Kravitz I see that https://github.com/HL7/davinci-pdex-plan-net/ is updated with version 1.0.0. Do you know when https://registry.fhir.org/package/hl7.fhir.us.davinci-pdex-plan-net%7C0.1.0 will be updated?
Saul Kravitz (Nov 25 2020 at 14:30):
@Fred Harmon We are ready to publish the STU1, but await withdrawal of negative ballots to bring the IG to the required threshold for publication. At that point http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1 will be available, and I assume the registry would be updated.
Fred Harmon (Nov 25 2020 at 14:31):
Thanks for the update Saul. Glad to see the progress.
Ryan Harrison (Dec 07 2020 at 17:51):
Thanks @Saul Kravitz!
Double checking my understanding...
1) When STU1 is tagged, the "Defining URLs" will also be available?
- Available now: Tip of
branch: master: https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/branches/master/StructureDefinition-plannet-HealthcareService.html - 404 now: "Defining URL" available when STU1 is "formally" released: http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-HealthcareService
2) To refer to a specific version, e.g. rest.resource.profile in our ConformanceStatement, we should use STU1 in the path?
- Don't use "Defining URL": http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-HealthcareService
- Rather, use STU1 in path: http://hl7.org/fhir/us/davinci-pdex-plan-net/STU1/StructureDefinition/plannet-HealthcareService
cc @James Fadeley
Saul Kravitz (Dec 07 2020 at 18:09):
@Ryan Harrison Good questions.
1) The canonical URL of the profile doesn't change across IG versions. Both the master and the to-be-published STU1 both refer to the same defining URL -- http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-HealthcareService
2) To refer to a specific version: I think you would want to refer to http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-HealthcareService|1.0.0, but consider this a tentative answer.
@Robert Dieterle @Dave Hill
Ryan Harrison (Dec 08 2020 at 00:43):
@Saul Kravitz
1) The canonical URL of the profile doesn't change across IG versions. Both the master and the to-be-published STU1 both refer to the same defining URL -- http://hl7.org/fhir/us/davinci-pdex-plan-net/StructureDefinition/plannet-HealthcareService
Absolutely correct...until R2 comes out (in many moons...stay with us please! :p). If we use the canonical without a version specifier, one would (wrongly) assume R2 instead of STU1.
Fred Harmon (Dec 11 2020 at 17:05):
@Saul Kravitz Any update on final publishing of this spec and subsequent registry package update?
Saul Kravitz (Dec 11 2020 at 17:07):
IG has completed all approval steps and is in the process of being published.
There is currently a technical hiccup beyond my control that is the only barrier to publication. I'm hoping that this will be resolved in the coming days. @Fred Harmon
Fred Harmon (Dec 11 2020 at 17:19):
Thanks as always for the quick reply @Saul Kravitz
Last updated: Apr 12 2022 at 19:14 UTC
