FHIR Chat · Who has implemented Patient/$everything ? · implementers

Stream: implementers

Topic: Who has implemented Patient/$everything ?


view this post on Zulip Eric Haas (Sep 29 2021 at 17:14):

Today in the International Patient Access IG Call, it was asked whether to add the Patient/[id]/$everything operation. Before any further discussion, we would like to know whether it or /Patient/[id]/$export alternative has been implemented or if is planned to be implemented 1-2 years.

  1. Patient/[id]/$everything returns: "In the US Realm, at a minimum, the resources returned SHALL include all the data covered by the meaningful use common data elements as defined in the US Core Implementation Guide. Other applicable implementation guides may make additional rules about how much information that is returned." async or sync

  2. vs in Bulk Data /Patient/[id]/$export operation export data on a patient in a server; it works async.

(note there is also an EHI Export which is an US federal ONC requirement to be able to export all data about an individual regardless of whether it's in the USCDI and regardless of whether it has been modeled in FHIR.)

view this post on Zulip Michele Mottini (Sep 29 2021 at 19:45):

We do not implement either, nor we have plans to implement them (we do implement normal bulk export and Patient/[id]/$everything)

view this post on Zulip Eric Haas (Sep 29 2021 at 20:58):

My mistake above, I meant Patient/[id]/$everything

view this post on Zulip Michele Mottini (Sep 29 2021 at 21:17):

We _do_ implement that then . . . but it is not very useful because it tends to return way too much stuff in one go

view this post on Zulip Alexander Zautke (Sep 29 2021 at 21:19):

We have implemented it in Firely Server, it’s also actively being used.

view this post on Zulip Cooper Thompson (Sep 30 2021 at 15:07):

We don't implement either, and have no plans. We do support Bulk Group/id/$export. We also support CCDA based exchange for sending "chart summary" style info. We prefer not to have multiple methods to do the same thing, as we have to maintain everything, which gets expensive.

I agree that neither Patient/id/$everything nor Patient/id/$export would cover the data required by EHI export. EHI export is much broader than FHIR can support currently.


Last updated: Apr 12 2022 at 19:14 UTC