microsoft / microsoft/fhir-server
"Unable to resolve reference to profile ..." error
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
Copied from https://github.com/microsoft/fhir-server/issues/3119 . The previous issue had a few different issues on there and some issues were already resolved. Breaking off into new one to address this particular issue:
We are also experiencing the same issue on the managed service. I tried both with a built-in profile (us-core-patient) and a custom profile, both are present in the service. Both validation outcomes give the "Unable to resolve reference to profile ..." error.
{ "resourceType": "OperationOutcome", "issue": [ { "severity": "error", "code": "incomplete", "details": { "coding": [ { "system": "http://hl7.org/fhir/dotnet-api-operation-outcome", "code": "4000" } ], "text": "Unable to resolve reference to profile 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient'" }, "location": [ "Patient // OperationOutcome.Location is deprecated, please use OperationOutcome.Expression" ], "expression": [ "Patient" ] } ] }
Contributor guide
Research direction
Start by reproducing validation with the built-in us-core-patient profile and a custom profile, using the OperationOutcome shown in the issue. Trace how the service resolves referenced profiles; done when validation resolves both profiles without the "Unable to resolve reference to profile" error.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100