The aim is to enable transfer of organization or organization unit work queue task and related patient data in the wellness application to the receiving system automatically based on rules set.

skenaario 1

The workflow has following steps:

  1. Receiving system subscribes notifications from relevant wellness app work queues (new tasks and updates) based on configurations provided by service
  2. Citizen fills symptoms assesment, gets recommendation to contact healthcare service provider and decides to do that via the system.
  3. Wellness system creates care plan for citizen and a task for healthcare service provider based on citizen municipality.
  4. Notification is sent (or pulled) to receiving system (FHIR Subscription). Notification is sent every time when new information is received from citizen related to task and patient data related)
  5. Receiving system (EHR) fetches (pulls) task and related information (Task and related patient data)
  6. Receiving system updates status and process continues in EHR
  7. Receiving system queries other task related patient data from sending system (if needed)

System roles

Systems name role
Sending system Server
Receiving system Client

Sequence diagram

Functional requirements

Functional requirements for Client (EHR):

FRC-1 : Client SHALL be able to fetch and query for FHIR resources via the Server’s FHIR API.

FRC-2: Client SHALL be able to update FHIR resources via the Server’s FHIR API

Functional requirements for Server (wellness app):

FRS-1 : Server SHOULD be able support the fetching and querying for the written resource

FRS-2: Server SHOULD be able to communicate the the possible use case specific tags on resources.

References

Nintiz eOverdracht FHIR IG (eReferral mechanism that uses FHIR) https://informatiestandaarden.nictiz.nl/wiki/vpk:V4.0_FHIR_eOverdracht#Using_Task_to_manage_the_workflow