Stream: FHIR HL7 test servers
Topic: Firely - Unable to resolve reference to profile
Corey Wen (Jun 17 2021 at 20:20):
I am trying to validate a Patient resource that follows the us-core-patient using the Firely server. I have been following Firely documentation for validation and trying the validation on a system and ResourceType level. However I get the error Unable to resolve reference to profile 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient'. To reference the us-core-patient I either put the canonical url in the endpoint like so
https://server.fire.ly/Patient/$validate?profile=http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient
or put it in the meta field for the resource
"resourceType": "Patient",
"meta": {
"profile": [
"http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient"
]
},
I managed to get the validation working using the FHIR validator jar [FHIR Validation tool Version 5.4.4 (Git# 952db0248a25)] for the Patient resource.
What might be the issue, such as if its an issue with the Firely server or the resource input.
Additionally, another situation when validating a bundle using the Firely server I receive no errors, but the FHIR validator jar returns errors such as Bundle entry missing fullUrl or Except for transactions and batches, each entry in a Bundle must have a fullUrl which is the identity of the resource in the entry; what could account for these differences?
René Spronk (Jun 29 2021 at 17:17):
Most probably the actual StrcutureDefinition of the referenced profile isn't available on the Firely server. Try making it available on the /administration endpoint of the Firely server. @Mirjam Baltus
Mirjam Baltus (Jun 29 2021 at 17:23):
Yes, this was indeed the case. The same question was posed in the #dotnet stream, where I've answered after reloading the profiles to the server.
Last updated: Apr 12 2022 at 19:14 UTC
