Stream: subscriptions
Topic: Radiology Use Cases for FHIR Cast
Jeremy Richardson (Jan 12 2018 at 17:57):
I work on a Radiology reporting package and we spoke with some folks at RSNA about FHIR Cast.
I'm a little confused as to the difference between FHIR Cast and Subscriptions.
I also see some info on replacing CCOW as a standard (which I think is a great idea), but FHIR Cast seems implies an EMR driven workflow to do basic patient/user context sharing, when CCOW was driver agnostic. This seems like a big limitation, especially in Radiology. Wondering if anyone can point me in the right direction to where the discussions are going on?
Grahame Grieve (Jan 12 2018 at 21:42):
right here, pretty much. FHIRCast is just a fancy name for FHIR subscriptions
Grahame Grieve (Jan 12 2018 at 21:42):
can you elaborate on why you think it's EMR driven workflow only?
Jeremy Richardson (Jan 12 2018 at 22:02):
Maybe it's just a missing example, but I see: "EHR notifies app of change" here: http://fhircast.org/#synchronize
I don't see an "App notifies EHR of change"
Grahame Grieve (Jan 12 2018 at 22:09):
@Isaac Vetter perhaps you can enhance this.
Isaac Vetter (Jan 12 2018 at 22:45):
Hey @Jeremy , I had hoped to describe this with:
For simplicity, the below describes an app synchronizing with an EHR, but any user-facing application can synchronize with FHIRcast. While less common, bidirectional communication between multiple applications is also possible.
But is sounds like that's not clear enough. Overall, the two roles are the "FHIR Server "and the "subscribing app". We are using the term EHR and app for these two roles.
I'll update the page to make the above, quoted sentence more explicit.
Isaac Vetter (Jan 12 2018 at 22:45):
Jeremy, do you see MModal playing the role of the "FHIR Server"?
Jeremy Richardson (Jan 13 2018 at 20:47):
@Isaac Vetter For some applications, yes. However I’m currently interested in context sharing, in particular user, Patient, exam (not sure what the fhir object is called)... in radiology, every reporting app/pacs combination has its own integration.
Jeremy Richardson (Jan 13 2018 at 20:49):
I’m trying to mentally map the use cases in fhircast to ccow but only see parts.
Jeremy Richardson (Jan 13 2018 at 20:50):
I’m a fhir novice, so I’m sure I’m missing some things
Jeremy Richardson (Jan 13 2018 at 21:26):
One set of questions I had from the patient sync example:
"focus" : [
"Patient/789",
"Encounter/100009181"
],
Is 789 the MRN? If so, is there a way to disambiguate different assigning systems?
If it's not the MRN and is the FHIR server's internal Patient ID, then the client would have to make an additional call to the FHIR server to understand how to map internally. If this is the case -- well it leads to more questions...
Grahame Grieve (Jan 13 2018 at 21:46):
yes it's an internal ID, and the client would either have to already have encountered that patient ID and know the patient, or it would have to look it up
Last updated: Apr 12 2022 at 19:14 UTC
