Open dattachandan opened 1 year ago
Hi Chandan - that URL https://build.fhir.org/ig/AuDigitalHealth/au-fhir-pd/branches/main/package.tgz looks wrong (is the internal agency fork I think, @robeastwood-agency ?) would normally be http://build.fhir.org/ig/au-fhir-pd/branches/main/package.tgz - I think this may have been automatically registered against the package by the build tools - I will investigate....
Hi Brett, Thanks. Is the FHIR version 4.0.1 and IG pack version 2.1.0 the current but not published to the public yet version in the CI build through the PR @robeastwood-agency mentioned in my earlier issue
Hi @dattachandan and @brettesler-ext - apologies for the delay, I have been on 3 weeks leave.
I will have a close look tomorrow and will respond - however, having fixed the issue re our internal fork package link, it may well now work as expected.
As mentioned yesterday, I have fixed the package link issue that resulted in the 404 [^1].
When I run something similar to your original validator command, it succeeds.
java -jar validator_cli.jar HealthcareService-example0.json -version 4.0.1 -ig hl7.fhir.au.pd#current
Results in
Success: 0 errors, 1 warnings, 1 notes
Information @ HealthcareService.specialty[0] (line 15, col4): None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set) (codes = http://snomed.info/sct#310000008)
Warning @ HealthcareService.specialty[0] (line 15, col4): ValueSet http://hl7.org.au/fhir/ValueSet/snomed-healthcareservice-specialties not found
A few other notes:
FHIR Validation tool Version 6.0.25
- note that the latest validator is now v6.1.16, and I'd strongly recommend using the latest.... -ig hl7.fhir.au.base#2.1.0 -profile http://hl7.org.au/fhir/pd/StructureDefinition/au-pd-healthcareservice
hl7.fhir.au.base
should likely be the latest 4.1.0-ig hl7.fhir.au.base#4.1.0
is mostly redundant, as the PD au-pd-healthcareservice profile is found by the validator and it is derived from the hl7.fhir.au.base#4.1.0 package anyway[^1]: the fix:
The validator processes the -ig hl7.fhir.au.pd
argument by looking over the wire for that package, looking in build.fhir.org/ig. Our AuDigitalHealth organisation contributions to the PD repository are via a GitHub fork that has also been configured to use the autobuilder. Following an update to master on the HL7AU PD repo, the autobuilder runs and the new hl7.fhir.au.pd
package can be found. However, when our fork has master synchronised, it also then autobuilds, and the new hl7.fhir.au.pd
package is somehow connected to our fork instead of the HL7AU source. The fix was simply to trigger an autobuild of the source HL7AU PD IG so that the hl7.fhir.au.pd
package gets associated to the source.
Hi team
I tried the validation CLI tool in the format and got this error - Invalid HTTP response 404 from https://build.fhir.org/ig/AuDigitalHealth/au-fhir-pd/branches/main/package.tgz
However, these 2 worked according to the available versions, although the warning and info notes were different from the AU base, not sure why pd shows 1 warnings, 1 notes while base shows 0 errors, 0 warnings, 3 notes ?
The AU base log
Further, noticed that the profile switch resulted in an Exception with the AU base as below.