CODEWITHSUNDEEP
notificationshl7-fhir
Joe Taras
Joe Taras

Reputation: 15399

FHIR manage of notifications

I'm trying to manage a FHIR workflow based on API Rest for resources CRUD (as Patient, Practitioner and so on).

For workflow handling among different systems I want to use task resource, but I don't want to manage the Subscription resource and it's architecture.

So I have a doubt about manage of notifications.

The correct way is: the different systems must apply a polling operation on server to know if there's a task resource to consume? Or is it the server to warn the different systems?

The server FHIR I want to use is R4.

EDIT

We want to create a interoperability platform about the exchange of data among three systems. Every system is already in production developed by different software house and we can't work on them.

Every system, actually, hasn't got a server FHIR (as the Option B of Workflow architecture).

Every system is available about communication in HL7 v.3 / FHIR

So we want to add a layer with FHIR Server as the below image.

Target architecture

In this case:

Upvotes: 0

Views: 429

Answers (1)

Lloyd McKenzie
Lloyd McKenzie

Reputation: 6803

The FHIR workflow communication patterns page defines a number of architecture alternatives. One possibility is to create the Task on the fulfiller's system. In that case, no need for polling or subscription. If the Task is created on the placer's system or an intermediary system and you're sticking with pure REST, then the fulfilling system will need to either have a subscription that will result in them receiving a notification about the Task or they'll have to poll. Other non-RESTful options include POSTing to a "process task" operation on the fulfilling system or sending a FHIR message to the fulfilling system.

Upvotes: 1

Related Questions