Stream: implementers
Topic: Who has both _history and _include implemented?
Simone Heckmann (Jan 03 2017 at 19:15):
I am currently looking for a server that has both the _history interaction for Observation as well as the _include search param implemented.
I don't need them combined I just want to poll a Server for any changes on Observations and then use a subsequent query to enricht the returned Observations with context (Patient, Encounter) to be able to generate V2 ORU messages from them.
I can't seem to find a server that supports both...
...anyone?
Grahame Grieve (Jan 03 2017 at 19:56):
mine does
Simone Heckmann (Jan 03 2017 at 20:11):
http://fhir3.healthintersections.com.au/open/Observation?_include:patient&_id=1361
..only returns the Observation, not the Patient.
Simone Heckmann (Jan 03 2017 at 20:11):
wrong syntax?
Grahame Grieve (Jan 03 2017 at 20:12):
yes your syntax for include is wrong
Simone Heckmann (Jan 03 2017 at 20:14):
http://fhir3.healthintersections.com.au/open/Observation?_include=Observation:patient&_id=1361
Simone Heckmann (Jan 03 2017 at 20:15):
yeah, that's working!
Simone Heckmann (Jan 03 2017 at 20:18):
There's no way to use the include on a instance level, like http://fhir3.healthintersections.com.au/open/Observation/1361/_include=Observation:patient?
Grahame Grieve (Jan 03 2017 at 20:42):
no but your search on _id is the same thing
Simone Heckmann (Jan 04 2017 at 19:11):
@Grahame Grieve :
Both _include and _revInclude use the wild card "*" for the search parameter name, indicating that any search parameter of type=reference be included.
Do you support this?
What's the synatx supposed to look like?
I tried this:
http://fhir3.healthintersections.com.au/open/Observation?_include=Observation:*&_id=1364
And got this: Unknown Resource Search Parameter '*'
Is this an unimplemented feature or is the syntax meant to be different?
Grahame Grieve (Jan 04 2017 at 20:43):
I don't think I support that yet
Grahame Grieve (Jan 04 2017 at 20:43):
I'll add it to my todo list
Simone Heckmann (Jan 04 2017 at 20:45):
ok, thanks. But syntactically that's what it would look like? Because the spec mentions it but doesn't give an example, so I wasn't sure.
http://fhir3.healthintersections.com.au/open/Observation?_include=Observation:*:Practitioner&_id=1364
or something alike would be legit as well, I suppose?
Grahame Grieve (Jan 04 2017 at 20:49):
I'm not sure. Seems reasonable
Simone Heckmann (Jan 04 2017 at 20:50):
yes, like "I don't care *where* it's referenced, but if it's a Practitioner, then include it..."
Grahame Grieve (Jan 04 2017 at 20:50):
you could make a task for us to ad an example or two...
Simone Heckmann (Jan 04 2017 at 20:52):
Let's first implement and test it, there's probably going to be other things that need examples or clarification, once we dig deeper...
Simone Heckmann (Jan 05 2017 at 09:07):
With _include=Observation:* (or other include statements) I might receive a bundle that contains multiple Observations. Is there a way to tell which Observation is the "focal" Resource that matched the search criteria and which are the included Observations? Is sort order the clue here?
Simone Heckmann (Jan 05 2017 at 09:13):
Wait. Sort order doen't make sense. There may be multiple focal Observations and multiple includes. You'd never be able to tell which is which...
Grahame Grieve (Jan 05 2017 at 11:02):
Bundle.entry.search.mode
Simone Heckmann (Jan 05 2017 at 11:05):
Ah great, thanks!
Simone Heckmann (Jan 05 2017 at 11:08):
The description of the _include says:
"For each returned resource, the server identifies the resources that meet the criteria expressed in the join, and adds to the results, with the entry.status set to "include" (in some searches, it is not obvious which resources are matches, and which are includes)."
Needs fixing, I guess. I will include (ha!) that in the tracker item.
Grahame Grieve (Jan 05 2017 at 11:11):
thx
Simone Heckmann (Jan 05 2017 at 11:24):
ok, next question:
Say I want to include every resource that an Observation references, I'd call
/Observation?_include=Observation:*
If I also wanted to include all references (no matter where) to Practitioner resources in the included DiagnosticRequests, I'd have to add
&_include:recurse=DiagnosticRequest:*:Practitioner
Now, if I wanted to include *all* Practitioners no matter where and no matter what the Resource type that references them, would this be possible:
&_include:recurse=*:*:Practitioner
?
Simone Heckmann (Jan 05 2017 at 12:34):
Last updated: Apr 12 2022 at 19:14 UTC
