honeymoose
/
hapi-fhir
mirror of https://github.com/hapifhir/hapi-fhir.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add MDM Expansion Docs (#4068) 

* Add docs

* Update hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_expansion.md

Co-authored-by: michaelabuckley <michael.buckley@smilecdr.com>

* Update hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_expansion.md

Co-authored-by: michaelabuckley <michael.buckley@smilecdr.com>

Co-authored-by: michaelabuckley <michael.buckley@smilecdr.com>
This commit is contained in:
Tadgh 2022-09-23 18:40:13 -07:00 committed by GitHub
parent ee1cb4e392
commit 2770295638
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa_mdm/mdm_expansion.md
View File

@ -18,6 +18,13 @@ GET http://example.com:8000/Observation?subject:mdm=Patient/1
This `:mdm` parameter qualifier instructs an interceptor in HAPI fhir to expand the set of resources included in the search by their MDM-matched resources. The two above HTTP requests will return the same result.
This behaviour is also supported on the `$everything` operation, via a slightly different mechanism. If you call the operation with `_mdm=true`, then MDM expansion will occur on the base Patient instance. For example:
```http request
GET http://example.com:8000/Patient/1/$everything?_mdm=true
```
This will first lookup all Patients linked to Patient/1, and then perform an `$everything` including all resources for these patients.
<div class="helpWarningCalloutBox">
One important caveat is that chaining is currently not supported when using this prefix.