ResourceReference should not resolve to Chained parameter #35
Comments
andy-a-o
added a commit
to andy-a-o/spark
that referenced
this issue
Sep 21, 2020
Alternative implementation that doesn't perform reference check when searching by references.
I made it enabled by default. It's also an option to disable it and return to the previous impl completely
or partially for the limited number of resources.
To return to the previous implementation having reference checks add this into `appsettings.json`:
```
...
"SparkSettings": {
...
"Search": {
"CheckReferences": true
}
}
...
```
Or, in `Web.config`:
```
<add key="SearchCheckReferences" value="true" />
```
To partially enable reference check for the limited number of resources add this:
```
...
"SparkSettings": {
...
"Search": {
"CheckReferences": true,
"CheckReferencesFor": ["Encounter"] // Encounter is just an example
}
}
...
```
and finally to partially enable reference check on resource property level use this example:
```
...
"SparkSettings": {
...
"Search": {
"CheckReferences": true,
"CheckReferencesFor": ["Encounter.subject", "Encounter.participant"]
}
}
...
```
Here's the `Web.config` analogue:
```
<add key="SearchCheckReferences" value="Encounter.subject,Encounter.participant" />
```
NOTE: index rebuild may be required if using absolute local URLs for storing references.
kennethmyhra
added a commit
that referenced
this issue
Sep 24, 2020
ResourceReference should not resolve to Chained parameter #35
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following search
~/fhir/Encounter?patient=d1
resolves to normalized criteria {patient.internal_id=d1}
Where it should just resolve to {patient=Patient/d1}
Because the encounter should be found even if the patient is not present in the database.
The text was updated successfully, but these errors were encountered: