Stream: IG creation
Topic: vsac mashup with example.org reference ???
Eric Haas (Nov 08 2021 at 21:14):
getting this error for an example instance in US Core (which has a vsac dependency) for an example.org reference.
output/Location-hospital.html#/html/body/div/div/div/div/div/div/p/a at Line 218, column 274 error The link 'http://fhir.org/packages/us.nlm.vsac/http://example.org/fhir/Organization/holy-healthcare/expansion' for "Holy Healthcare" cannot be resolved
here is the example:
resourceType: Location
id: hospital
meta:
extension:
- url: 'http://hl7.org/fhir/StructureDefinition/instance-name'
valueString: Hospital Location
- url: 'http://hl7.org/fhir/StructureDefinition/instance-description'
valueMarkdown: This is an example hospital location for the *US Core Location Profile*.
profile:
- 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-location'
status: active
name: Holy Family Hospital
telecom:
- system: phone
value: '9786870156'
address:
line:
- 70 EAST STREET
city: METHUEN
state: MA
postalCode: 01844
country: US
# =================== SOURCE OF ERROR =================
managingOrganization:
reference: 'http://example.org/fhir/Organization/holy-healthcare' # <<<<<< this is the reference using 'example.org'
display: Holy Healthcare
# =======================================================
is there something I am doing wrong here or is this some weird quirk of the publisher?
Grahame Grieve (Nov 09 2021 at 05:18):
how would I reproduce this?
Eric Haas (Nov 09 2021 at 18:15):
I was able to reproduce in my test build...
- added this example
{"resourceType":"Location","id":"hospital","meta":{"extension":[{"url":"http://hl7.org/fhir/StructureDefinition/instance-name","valueString":"Hospital Location"},{"url":"http://hl7.org/fhir/StructureDefinition/instance-description","valueMarkdown":"This is an example hospital location for the *US Core Location Profile*."}],"profile":["http://hl7.org/fhir/us/core/StructureDefinition/us-core-location"]},"status":"active","name":"Holy Family Hospital","telecom":[{"system":"phone","value":"9786870156"}],"address":{"line":["70 EAST STREET"],"city":"METHUEN","state":"MA","postalCode":"01844","country":"US"},"managingOrganization":{"reference":"http://example.org/fhir/Organization/holy-healthcare","display":"Holy Healthcare"}}
and 2) these dependencies to the IG resource:
"dependsOn": [
{
"packageId": "hl7.fhir.us.core",
"version": "4.0.0",
"uri": "http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core",
"id": "hl7_fhir_us_core"
},
{
"id": "vsac",
"packageId": "us.nlm.vsac",
"uri": "http://fhir.org/packages/us.nlm.vsac/ImplementationGuide/us.nlm.vsac",
"version": "0.3.0"
}
],
Eric Haas (Nov 09 2021 at 18:25):
added a second example to verify and every link with "reference": "http://example.org/fhir/.... causes this error
Grahame Grieve (Nov 09 2021 at 20:01):
do you want to commit to a branch so I can test?
Eric Haas (Nov 09 2021 at 21:01):
branch here: https://github.com/Healthedata1/Sushi-Sandbox/tree/20211109_test
this is a strictly local testing build and input in input (you can ignore the yml) and fsh-generated outputs to docs for gitpages and no webhook to CI build. It uses sushi to create the menu and ig resource.
Grahame Grieve (Nov 10 2021 at 01:25):
I can't run that:
Grahame Grieve (Nov 10 2021 at 01:25):
Sushi: error Unable to determine path context for rule indented 1 space(s). Rules must be indented in multiples of 2 space(s). (00:00.0677)
Grahame Grieve (Nov 10 2021 at 01:25):
Sushi: File: C:\work\org.hl7.fhir.igs\Sushi-Sandbox\input\fsh\my-profiles.fsh (00:00.0678)
Sushi: Line: 38 (00:00.0678)
Eric Haas (Nov 10 2021 at 02:05):
ok it runs without sushi now
Grahame Grieve (Nov 10 2021 at 03:37):
Publishing Content Failed: Error loading template /Users/ehaas/Documents/FHIR/ig-template-base: Unable to load template from /Users/ehaas/Documents/FHIR/ig-template-base cannot find template. Use a github URL, a local directory, or #[folder] for a contained template (00:00.0775)
Eric Haas (Nov 10 2021 at 07:02):
ok sorry ... updated
template = fhir.base.template#current
Grahame Grieve (Nov 10 2021 at 21:42):
fixed next release
Monique van Berkum (Nov 15 2021 at 21:22):
@Grahame Grieve After the fix, we are still getting this QA message for an example instance in our IG (which has a vsac dependency):
image.png
Component[0] and Component [1] in the example (below) meet the criteria. I think the issue is access to vsac to validate the code:
"component": [
{
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "72826-1",
"display": "Race OMB.1997"
}
]
},
"valueCodeableConcept": {
"coding": [
{
"system": "urn:oid:2.16.840.1.113883.6.238",
"code": "1002-5",
"display": "American Indian or Alaska Native"
}
]
}
},
{
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "72826-1",
"display": "Race OMB.1997"
}
]
},
"valueCodeableConcept": {
"coding": [
{
"system": "urn:oid:2.16.840.1.113883.6.238",
"code": "2106-3",
"display": "White"
}
]
}
},
Grahame Grieve (Nov 15 2021 at 21:23):
I don't believe that's related to the fix
Monique van Berkum (Nov 15 2021 at 21:31):
@Grahame Grieve It was present before the fix, but we hoped it would resolve after the fix. Was that an incorrect assumption.
Monique van Berkum (Nov 15 2021 at 22:08):
Do you prefer that I suppress the message or leave it as a reminder that this needs fixing?
Grahame Grieve (Nov 15 2021 at 22:15):
I don't need a reminder generally - fixing vsac is definitely on my todo list
Grahame Grieve (Nov 15 2021 at 22:15):
so it's up to you
Last updated: Apr 12 2022 at 19:14 UTC
