ensure in-memory matching location search for Dstu3 falls back to a db search
This commit is contained in:
parent
2bc3181218
commit
a63c62b2e1
|
@ -42,6 +42,7 @@ page.server_jpa.introduction=Introduction
|
|||
page.server_jpa.get_started=Get Started ⚡
|
||||
page.server_jpa.architecture=Architecture
|
||||
page.server_jpa.configuration=Configuration
|
||||
page.server_jpa.search=Search
|
||||
page.server_jpa.upgrading=Upgrade Guide
|
||||
|
||||
section.interceptors.title=Interceptors
|
||||
|
|
|
@ -0,0 +1,18 @@
|
|||
# JPA Server Search
|
||||
|
||||
The HAPI FHIR JPA Server fully implements most [FHIR search](https://www.hl7.org/fhir/search.html) operations for most versions of FHIR. However, there are some known limitations of the current implementation. Here is a partial list of search functionality that is not currently supported in HAPI FHIR:
|
||||
|
||||
### Date searches without timestamp
|
||||
|
||||
Searching by date with no timestamp currently doesn't match all records it should. See [Issue 1499](https://github.com/jamesagnew/hapi-fhir/issues/1499).
|
||||
|
||||
### Chains within _has
|
||||
|
||||
Chains within _has are not currently supported for performance reasons. For example, this search is not currently supported
|
||||
```http
|
||||
https://localhost:8000/Practitioner?_has:PractitionerRole:practitioner:service.type=CHIRO
|
||||
```
|
||||
|
||||
### Location.position "near"
|
||||
|
||||
Searching on Location.Position using `near` currently uses a box search, not a radius search. A box search is a square centred on the provided coordinates with the shortest distance to the edge of the square equal to the distance provided; this means the box search will match more locations than a radius search in the corners. Currently, distance is assumed to be in km and any provided units are ignored. Distance must be between 0.0km and 10,000km.
|
Loading…
Reference in New Issue