You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2019. It is now read-only.
The FHIR spec for Encounter$everything operation seems to indicate the response should include all referenced resources for the encounter, as well as what the server may deem associated.
I would assume the CarePlan is associated, but I'm wondering if you have reasons not to include it in the response.
Note: This FHIR.org API does include CarePlans in the Encounter$everything response.
The text was updated successfully, but these errors were encountered:
CarePlans associated with an encounter are not represented as a resource in the
$everything
response for an Encounter.For instance this CarePlan has a
context: { reference: "Encounter/58b3663e3425def0f0f6a22a" }
, but the CarePlan is not a resource listed in the $everything query for that Encounter.The FHIR spec for
Encounter$everything
operation seems to indicate the response should include all referenced resources for the encounter, as well as what the server may deem associated.I would assume the CarePlan is associated, but I'm wondering if you have reasons not to include it in the response.
Note: This FHIR.org API does include CarePlans in the
Encounter$everything
response.The text was updated successfully, but these errors were encountered: